In this video we'll take a look at engine exis design as a reverse proxy server and see how it compares
to Apache.
By default.
Apache is configured in what's called pre fork mode meaning that had spawned a set number of processors
each of which can serve a single request at a time regardless of whether that request is for appear
to be script or an image.
Engine X on the other hand deals rutha requests asynchronously meaning that a single engine exe process
can serve multiple requests concurrently with that number basically just depending on the system resources
available to the engine x process.
That said because if there's a synchronous design engine X unlike Apache can't embed server side programming
languages into its own processes meaning that all requests for Dynamic Content has to be dealt with
by a completely separate process like p.h. B if P. M. and then reverse proxy back to the client via
engine X..
Now this might sound somewhat overcomplicated but it's actually fairly simple to set up and will cover
it in depth.
Of course not having to deal directly with embedded programming languages like Apache does makes engine
X a lot less resource hungry.
Now this doesn't mean that the resources used for the processing of server side languages is simply
freed up.
Rather they are being allocated elsewhere like in the most common case of BHB to the p s p f P. M. process.
But it does mean that unlike Apache server side language modules don't need to be run for every single
request the server receives instead.
Engine X will handle serving static resources without BHB ever knowing about it.
Whereas Apache will handle every request with that costly overhead.
And this is exactly where the real world savings on system resources come into effect.
So essentially a well configured engine XT web servers serving mixed content meaning both static and
dynamic resources should always be more efficient and less demanding on system resources than a similar
Apache set up.
How does this relate to performance then you most likely read or heard that engine X is faster than
Apache.
After all one of engine Xist Corps develop and focus this was that of performance.
But it's really important to first define what's meant by fast.
Engine X can't magically deliver data to the client any faster than the internet connection will allow.
But it can a serve static resources much faster than Apache and B handle a much larger number of concurrent
requests.
Remember engine X will serve static resources without the need to involve any server side languages.
And this gives it quite an advantage over Apache.
And as for handling concurrent requests engine X can potentially receive thousands of requests on a
single processing thread and respond to them as fast as it can without turning down any of those requests.
Apache on the other hand will accept a request up to the preconfigured number and then simply reject
the rest.
So if we define performance or being fast in terms of how many clients can be served under high load
assuming the usual mix of static and dynamic resources then yes engine exist differently faster than
Apache.
Engine X is configuration also takes a very different approach to have patches in their requests.
I interpret it as you are right.
Locations first whereas Apache default to and highly favours filesystem locations.
This preference for file system locations can also be seen in the use of h.t. access files for overriding
specific directory configurations.
Engine X doesn't offer any similar functionality.
But seeing as apache's h.t. Axis overrides carrière significant performance penalty.
They shouldn't really be considered an advantage.
It's also because of this very design of interpreting requests.
As you are locations that allows engine extra easily function as not only a web server but anything
from a load balancer to a mail server.
That brings us to the end of this video and hopefully you now have a better understanding of what engine
X is and why we want to use it in the next section of the Course we'll get started with installing engine
X..