3 ms·
it seems too me like kubernetes aims to replace the existing service-mesh consisting of de facto microservices (load-balancers, remote-logging, systemd, xinetd,
by fock 7y ago
it seems too me like kubernetes aims to replace the existing service-mesh consisting of de facto microservices (load-balancers, remote-logging, systemd, xinetd, ...) bonded by unixy conventions with.... a monolithic, proprietary system. Proponents are then advocating to build decoupled microservices on top of this. Am I the only one who thinks this is shizophrenic?
(on the other hand: companies claiming to make the world a better place by selling ads to the highest bidder are shizophrenic...)
- theK 7y agoI’m positively attuned to the ... de facto Microservices bonded by unixy conventions ... part. And it has worked well in the past. You had much more freedom but everyone needed to pretty much roll their own. Kubernetes is a compromise on that. You don’t need to build you ops framework from scratch now and deploying something has very well defined APIs. OTOH you now are in a world of finding which k8s extensions/plugins/whatever you should use and which are just “fancy”. And answer questions like Is Knative V0.8 good enough for our workloads? Because Ai Defi needs that for some reason... EDIT: Kubernetes is open source though right?
- fock 7y agoyeah it is open source, but half a million loc for a simple admin tool seems like the perfect path to vendor lockin ;)
- ex_amazon_sde 7y agoThis is exactly what lock-in looks like.