-
Notifications
You must be signed in to change notification settings - Fork 98
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How does this compare to others? #689
Comments
Hi @warvstar, thanks a lot for the interesting questions. k8gb is an open-source, Kubernetes-native, and cloud vendor agnostic solution. We tried to highlight main project differentiators here https://github.com/k8gb-io/k8gb#key-differentiators Just to fully clarify, the main goal of the project is not CDN-like proximity but cross-region highly availability. Currently, we achieve it with round-robin and failover strategies. Still, for the closest geolocation functionality, we have We in Absa Group(where the project was originally started) are using k8gb for global load balancing between 2 distinct datacenters for on-prem scenario, and between the regions in the case of AWS. |
@warvstar please also check in-depth article on GSLB by our friends from Redhat https://cloud.redhat.com/blog/global-load-balancer-approaches |
@warvstar hope it answers your questions, closing, feel free to reopen in case you want to continue the conversation |
Okay so I'm just getting involved in k8s now, and load balancers.
I currently use AWS load balancers attached to AWS Global Accelerator (anycast), as I was primarily using ec2 servers directly.
Now I'm looking into using containers and scaling across cloud providers. Can I still use AWS for this? Should I use k8s? What about Github's Load Balancer director?
I know I just said I'm interested in multicloud, but what if I didn't want to do multicloud, would there be a reason to use anything other than my current setup for load balancing?
My use case is this is: I have some immutable data stored in memory, I want users from all over the world to be able to connect to the closest (or fastest?) server near them, so they can download these assets as quickly as possible (generally via websockets, as downloading 1000s of assets via GET requests has overhead that I measured to be unacceptable.)
Basically like a CDN; the only reason I'm not using a CDN is because from my tests, even if they have edge locations in my city, it can be quite a bit slower downloading via GET requests and also because I'd like more control over my cache. On my machines I can keep recently accessed data in memory for as long as I'd like.
Also, if anyone knows of a cost and performance equivalent or better using serverless, then I'd be interested in knowing about that as well.
Btw, I'm willing to pay for help and advice here, thanks all!
The text was updated successfully, but these errors were encountered: