Handle 50000 concurrent connection

I have a static site. The site would have just some javascript and static content. I need to handle about 50,000 concurrent visitors. Can anybody explain which kind of architecture and technology is needed (e.g. single server / ngnix load balancing / …)

Show comments

Submit an answer

This textbox defaults to using Markdown to format your answer.

You can type !ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

Sign In or Sign Up to Answer

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Want to learn more? Join the DigitalOcean Community!

Join our DigitalOcean community of over a million developers for free! Get help and share knowledge in Q&A, subscribe to topics of interest, and get courses and tools that will help you grow as a developer and scale your project or business.

@roby <br> <br>It’s hard to make generalizations. The best thing to do would be to spin up some droplets and do some load testing of your set up. Consider throwing something like Varnish up in front of nginx to do some caching.

50000 is the highest amount of connection at one specific time, Average concurrent connection will be lower. <br> <br>Tnx

Are you sure you will be getting 50000 concurrent connections? That equals approx. 129,600,000,000 connections per month. <br> <br>Nginx works pretty well for static websites, you can start off with a 2GB droplet (in order to get 2 CPU cores) and scale up if needed. Make sure you set nginx to use 2 worker processes (<code>/etc/nginx/nginx.conf</code>). <br> <br>If you won’t be getting that amount of traffic, a 512MB droplet will do just fine.