How to Handle 10,000 Concurrent Users

theskilledcoder's tweet image. How to Handle 10,000 Concurrent Users

you could handle 10,000 concurrent users on a single server depending on what the backend needs to be doing. heavy computation obviously not, but if this is for a website, even with logins, and medium computation like databases and table calls, you dont need all that. just use…


Yes this will work for many use cases especially if traffic pattern is predictable My breakdown leans toward general-purpose, elastic systems where traffic can spike, teams are distributed, and infra needs to scale out cleanly


If using postgresql, Dont need Redis for caching queries. We can use shared buffers


, 🤣 You haven’t seen yet single server handling 20 000 users and coping fine


Good stuff


One at a time, switching really fast..


I will intern in a company that makes all these infrastructure decisions for a month


who reads photos with small fonts? write it in text format, like a normal person would


Cool bro, will look into this once my SaaS reaches 10,000 concurrent users.


This post is unavailable.

AWS infrastructure with ELB and horizontal scaling: Number of connections on the first day of ticket redemption for the Estudiantes/Gimnasia soccer derby.

cmgodoy's tweet image. AWS infrastructure with ELB and horizontal scaling: Number of connections on the first day of ticket redemption for the Estudiantes/Gimnasia soccer derby.

10k concurrent users Cache Sqlite on memory Db sqlite (only reads) Any backend Monolit with 1gb ram 2 core Happy code


This is good


Great Approach.


United States Trends
Loading...

Something went wrong.


Something went wrong.