From PHP and on-prem servers to NodeJS/React and AWS
summary
Rewrites a high‑traffic portal (about 50 million page views and >1,000,000 monthly users) from PHP/on‑prem to NodeJS/React on AWS, using Lambdas, Docker on ECS and CloudFlare. Builds a per‑minute static HTML snapshot in S3 static fallback that serves during outages, uses dynamic imports for bundle splitting and UA‑driven server vs client rendering to cut transfer costs (client‑side saves ~50% on traffic; SSR adds ~30% infra cost), and survives third‑party ads with uncontrolled components. Peak capacity targets around 1,000 requests per second.
AI-written summary · about
chapters (10)
- 0:00Start
- 3:29Infrastructure challenges
- 5:46Availability & Balancing
- 8:27Static assets & Traffic costs
- 10:02And when you do it right, you can actually end up having your entire infrastructure in your git repo.
- 10:39Javascript challenges
- 10:49Handling errors
- 12:59Page first load
- 14:20Crawlers & Old browsers
- 17:18Dealing with aggressive ads
related talks
17mBuilding a High Performance, Dynamic CDN with Next.js
33mWeb performance in large-scale applications
46mPushing the limits of PHP with React PHP
19mMigrating from legacy platforms to node
31mNode.js that's hugely reliable, fast, and scalable
32mUI @ Flipkart: A Node Direction
58mMassively Scaled High Performance Web Services with PHP
23mRevamping How Node.js Binaries Are Served At Scale