PHP is the king ...
summary
E-commerce platform scales from a LAMP monolith (PHP, Nginx, MySQL, Memcache, Solr) to an SOA with millions of monthly visits and ~50 engineers in the tech team, splitting functionality into bundles (Symfony/Silex) and light services. Async work uses RabbitMQ queues with PHP consumers supervised by supervisor, memcache gets replaced by Redis for persistence, client uses AngularJS for mobile and Node/Express server‑rendering for desktop, JWT/JWS via jose library handles stateless sessions, Docker is rolling into production. Mock servers and smoke tests speed development; one developer rebuilds the site in two weeks.
AI-written summary · about
chapters (20)
- 0:00Introduction and disclaimer
- 0:26Company and project overview
- 3:13Monolithic architecture beginnings
- 3:53Transition to SOA architecture
- 8:09HTTP protocol importance
- 10:17Asynchronous communication with queues
- 15:14Switching to Symfony framework
- 19:07Building single-page applications
- 22:42Stateful to stateless architecture
- 24:46Desktop website challenges
- 26:49Node.js for rapid development
- 28:15API testing and mocking tools
- 30:05Replacing Memcached with Redis
- 31:51Python and mobile app integration
- 33:37HTTP protocol for mobile developers
- 33:58Docker adoption and benefits
- 38:12Current architecture overview
- 39:15Future plans and technologies
- 40:39Learning from other languages
- 42:01Q&A session
related talks
01mPHP is more alive than ever
58mMassively Scaled High Performance Web Services with PHP
37mHow to run 200+ PHP services in production and not lose your mind
18mMy Take on PHP
29mPanel Discussion
01h 04mI saw the future, and its web servers were written in PHP
36mWe're gunna program like it's 1999
52mPHP at the Firehose Scale