I have kubernetes cluster set up that hosts graphql api server https://hasura.io. 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?
Become a contributor for community
Get paid to write technical tutorials and select a tech-focused charity to receive a matching donation.
DigitalOcean Documentation
Full documentation for every DigitalOcean product.
Resources for startups and AI-native businesses
The Wave has everything you need to know about building a business, from raising funding to marketing your product.
The developer cloud
Scale up as you grow — whether you're running one virtual machine or ten thousand.
Start building today
From GPU-powered inference and Kubernetes to managed databases and storage, get everything you need to build, scale, and deploy intelligent applications.
