2 ms·
Nginx/Apache/Caddy + php-fpm + something like MySQL if your database lives on the same server as your application. PHP in its default form isn’t a persistent pr
by deergomoo 2y ago
Nginx/Apache/Caddy + php-fpm + something like MySQL if your database lives on the same server as your application. PHP in its default form isn’t a persistent process[0], so you will typically have a web server accepting the requests and forwarding them onto PHP to generate a response.
0: it actually usually is these days for performance reasons, with a pool of processes that are reused. But the mental model is one short-lived process per request
- hipadev23 2y agoand if the Go dev needs a database, or a cache, or an actual fully-featured HTTP daemon processing the requests? I’m just confused about their focus on “single binary” when applications in those languages tend to be a single-container plus the same supporting services their single binary is going to need too.