Timeline for What is the purpose of running PHP-FPM in its own container instead in the same container as apache2/nginx?
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 30 at 22:50 | history | edited | unity100 | CC BY-SA 4.0 |
Typos
|
| Jan 30 at 16:58 | comment | added | 8None1 | Great information here. One issue I didn't see addressed was logging output. Much of the docker/podman/k8s architecture assumes a single log output for that single process (in its single container). Though it's more of an inherited requirement of containerization and I've worked around the rule, it's always been a regret. | |
| Mar 24, 2021 at 20:17 | history | edited | unity100 | CC BY-SA 4.0 |
added 508 characters in body
|
| Feb 4, 2021 at 16:23 | vote | accept | aK8sN0v1c3 | ||
| Feb 4, 2021 at 16:22 | comment | added | aK8sN0v1c3 | This is as good of a "working theory" answer that could be expected. Thank you for the detail in your hypothesis. I, too, would like to see benchmarks! Breaking each service out into it's own pod/container is adding more complexity than worth the potentially and occasional benefits to scalability, IMO, also. The expense of a smaller instance/pod/container is negligible in the face of benefits to elegance and consistent performance. I do agree edge-case workloads my benefit from service/server separation tho not the norm. Triggers for auto-scaling + warm-up times are key factors in a CBA. | |
| Feb 1, 2021 at 9:47 | history | edited | unity100 | CC BY-SA 4.0 |
corrected pods to services
|
| Jan 31, 2021 at 21:44 | history | edited | Pierre.Vriens♦ | CC BY-SA 4.0 |
deleted 273 characters in body
|
| Jan 31, 2021 at 19:34 | review | First posts | |||
| Jan 31, 2021 at 21:44 | |||||
| Jan 31, 2021 at 19:32 | history | answered | unity100 | CC BY-SA 4.0 |