Re:Google admits Kubernetes container tech is too complex
by arcturus17 on Friday February 26, 2021 @01:59AM
(#26272041)
Even if your default starting stack is somewhat complex, for example, separate client and server apps, database, cache, and queue, most one-click cloud providers (ex Heroku or ElasticBeanstalk) offer ways of unifying logs, monitoring, simple provisioning, etc. You are “locked-in” in that you can’t move to another provider within an hour, but the lock-in would still be very low, you can use generic technologies (ex: Memcached or Redis) and have an impact only on a few config files...
I’m not telling people what to do, if you like K8s or Docker or what have you knock yourself out, and I mean it. For example, people keep telling other people on HN not to use React and that’s a hill I’d die on - and could write a dissertation defending it. I’m just wondering what the dev experiences of others are so I may learn from them.
When you start having a lot of pieces to manage eg. cache, database, auth, multiple applications then Kubernetes comes into its own.
Because then you can scale, monitor, trace, debug, log, backup, audit, encrypt and visualise all of those pieces in exactly the same way.
And do it irrespective of which cloud you use or whether it's even in the cloud at all.