Powering 100+ million daily users
summary
Architecture that serves 100+ million daily users with a claimed 250 ms top card render and a 93% cache hit ratio using Redis clusters with consistent hashing, regional replication, and prefetching heuristics. Uses SignalR then moves to WebSockets with REST-over-WebSocket to avoid TLS handshake latency and IP‑affinity hotspots. Describes an organized‑monolith pattern (domain DLLs, shared libs) to evolve safely into microservices; explains failures, profiling, and resource tradeoffs that drove each change.
AI-written summary · about
chapters (7)
- 0:00Introduction and project goals
- 5:23Architecture and scaling
- 12:36Geo-distribution and availability
- 16:45Optimizing performance
- 23:13Communication protocols
- 32:22Engineering structure
- 45:15Conclusion and Q&A
related talks
42mPowering 100+ million daily users
23mMicroservices – Diptanu Choudhury
22mMicroservices Highway to hell
41mArchitecting Business-Driven .NET Microservices in the Cloud
41m.NET Microservices in Real Life
55mArchitectural Patterns for Rapid, Reliable, Frequent and Sustainable Development
46mFrom Monolithic Monster to Majestic Microservice App
10mMicroservices, Messaging, and Failure: How Simplifying Our Architecture Saved Us