How to run 200+ PHP services in production and not lose your mind
summary
A case study from a large Ukrainian e‑commerce project evaluating PHP for service-oriented architecture in 2025. Covers how to achieve performance, autoscaling, monitoring, centralized tools and development standards in PHP, and presents practical patterns, common pitfalls and ready templates used to run 200+ PHP services in production.
AI-written summary · about
chapters (19)
- 0:00Introduction
- 1:26400+ PHP services architecture
- 2:50Framework choice
- 4:36Unified service pack
- 6:45External service comms issues
- 7:48API Gateway with Node.js
- 8:51Internal service comms
- 9:55Async via queues
- 10:17PHP service structure
- 11:43Open Swoole for requests
- 13:07State cleanup & parallel exec
- 14:11Prometheus metrics
- 16:01PagerDuty alerts
- 17:03Sentry logging
- 19:59Auto-scaling strategy
- 22:55Code quality & testing
- 24:19Open Source bundles
- 25:01Q&A
- 36:35Closing remarks
related talks
45mPHP is the king ...
34mMigrating a High‑Load Project to Microservices
58mMassively Scaled High Performance Web Services with PHP
37mScaling LAMP doesn't have to suck
42mHighload at the Intersection of DevOps and PHP Development
43mGo micro with Microservices
33mRunning PHP-Applications in a Multi-Process Container
44mThe Yellow Brick Road: Taking Microservices Home in Large Enterprises