Today has been a complete debacle. I do not quite understand how a website can crash almost immediately upon receiving traffic.
Scalability == Capacity * Density
WorkloadCharacterization List of events Read workload (mostly) scheduled updates minimal consistency requirements (minutes) Status of active event Read workload, continuous concurrent updates during events. ~ 3-5 second read consistency Status of active event (mobile) Read workload, continuous concurrent updates during events. ~ 3-5 second read consistency. Push notification on “interesting” update.
1Compute instances for front-end / back-end web sites 10 dedicated instances (call support for more) 2Concurrent active sockets (e.g. WebSocket) 350 / dedicated instance (can be increased) 3Requests/sec per VM Metered by efficiency of implementation 4Connections / database Capped at 180 (default ASP.NET pool size is 100) 5Database throughput Multiple metered resources, efficiency of implementation subscription-service-limits/
1Internal logic errors or exceptions in application code By and large, IIS will save you from intermittent errors (or at least limit them to a single request) 2Single SQL DB instance Any transient or enduring errors here will have a drastic effect on the web experience
?