Backend Devs Build Systems that make peoples lives a bit easier Design End to End Software for Digital Insurance Companies in Nigeria Some open source contributions to Dokku Kubernetes Scheduler
applications Create middleware applications, using as many layers as you want, and the architecture your project needs. Used to be Zend Expressive https://docs.mezzio.dev/mezzio/
and response, and which can take the incoming request, perform actions based on it, and either complete the response or pass delegation on to the next middleware in the queue.
engine for handling requests — for instance, you could have middleware perform the following • Handle Authentication • Manage Access Control • Logging, etc.
Web Server • PHP process is triggered • Application is bootstrapped and loaded • Request is processed • Response is returned • Dispose everything and start again for new request
up webserver • Application is bootstrapped and loaded • Dispatch to web worker • Request is processed • Response is returned • Keep Application state in memory for subsequent HTTP requests
the PHP application once, and then keeps it in memory so that it can continue dispatching requests without having to load resources every time. This makes it really fast. HTTP requests are handled by a set of child processes called “web workers”. Swoole forks the contents in memory for the main process to each one of the workers, so each worker has a “copy” of the application in memory. Each worker is independent, but each one of them can only handle one request at a time, so you have to increase the number of workers if you expect a lot of concurrent traffic.