|
|
|
|
|
by zug_zug
36 days ago
|
|
I mean dude, most of us did high-availability before kubernetes existed. Kubernetes didn't solve any unsolved problem, it just moved it from a gui to yaml. You just used a load-balancer (an AWS one preferably) with a few machines behind it, optionally an auto-scale group. AWS has multi-region support built in. Re: file descriptors -- that's not something handled by kubernetes, if anything you just have more layers now. You don't need service discovery, you never did, Host your services at a private zone {service-name}.{env}.company.com zones which points to the loadbalancer. You need monitoring and should use an observability solution for that, has 0 to do with kubernetes. You're just taking a bunch of random entirely solved problems and for some reason suggesting kubernetes is somehow helpful for them. |
|
You do need service discovery at some point at scale if you are using any kind of distributed system. that is quite a strong claim. what do you have to support that claim?
You sound like you’ve never really seen scale and I’m not sure how to respond in a way that is polite. It is heavily dependent on your use case and industry. if you can get by with docker containers, good for you! My only point is you are probably reinventing the wheel here.