Understanding Load Balancer limits with graphql / websocket subscriptions

I have kubernetes cluster set up that hosts graphql api server This cluster is exposed to “the world” via digital ocean’s load balancer service.

After reading through load balancer limitations documentation I am concerned about two specific ones: 60s keep alive limit and max of 10,000 concurrent connections.

As my graphql api server exposes subscriptions through web-sockets and is used to power mobile game that relies on this live data, these limits can be reached relatively fast.

Hence I wanted to clarify if I understand these limits correctly and if they are indeed a concern for my use case. If so are there any alternatives to Load Balancers that I could utilise in this scenario?

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.

As user needs have increased we’ve actually released additional sizes for load balancers so that you can create larger nodes that support up to 40,000 concurrent connections, you can also find out more information that here: