ToPlay on Google Cloud
summary
A web app for festival signups deployed on Google Cloud uses Cloud Run, Firebase (Auth, Hosting, Storage, Firestore), Algolia, a Quarkus backend and a Next.js frontend to manage 10,000 games and production traffic (863 users, 57 associations, 2,257 seats, 1,061 bookings). The frontend autoscaled to six Cloud Run instances while the backend stayed at one to avoid cold starts and handled about 1,000 concurrent users; main problems were high Firestore read costs and unoptimized images, addressed with a backend second-level cache and a CDN plus image optimization.
AI-written summary · about
chapters (11)
- 0:00Welcome
- 3:59Firebase services
- 9:15Cloud Run serverless
- 12:01Quarkus GraalVM backend
- 16:15Text search Algolia
- 18:42Next.js SSR frontend
- 22:35Event results metrics
- 26:03Cost analysis optimizations
- 27:51Web mobile demo
- 31:43Next steps community
- 32:47Q&A
related talks
45mGenesis of websites on Google Cloud
39mHow GCP Helped Me Save My Production at Mamie’s
51mCloud Native Development Level Up for Smaller Teams
10mAirAsia DevOps Journey
30mCI/CD for Hybrid and Multi-Cloud Customers
27mGrowing your Cloud application
19mEverything I learned about dynamic scaling of cloud apps.
43mBuild and deploy a serverless web app on GCP