4 ms·
Looks like we're starting to see k8s slide down the slope in the typical "hype cycle", in the way we've seen Docker do so over the last 12-18 months. It'll be
by rtempaccount1 7y ago
Looks like we're starting to see k8s slide down the slope in the typical "hype cycle", in the way we've seen Docker do so over the last 12-18 months.
It'll be interesting to see how well it weathers this part of the cycle and comes out the other side.
For me k8s is useful but overhyped, leading to many companies making use of it when it really wasn't needed (I've seen k8s cluster deployed for single applications !?!)
It has a lot of complexity (far more than just Docker/Docker-compose style stacks) which are only likely to make sense at scale.
The thing that makes me thing k8s will suffer, is that complexity is increasing not reducing. Things like adding service mesh layer, use of operators, CRD etc are all additional complication on top of what is a moderately complex product.
- z9e 7y agoReminds me when Hadoop was going through it's hype cycle and I saw people installing it for a 10gb data set.
- tonyarkles 7y agoBut... but... 10GB is REALLY BIG DATA :) You can't open that in Excel!
- jjeaff 7y agoKubernetes is complicated. But not so bad with hosted options like gke. I put my relatively small app on it. We have just 3 nodes. One for database and the other 2 for application and supporting pieces like redis, and elk stack for reporting. Docker compose doesn't work for more than a single node. I initially started using k8s for seemless deployment of updates in our CI. Anything with docker alone was beginning to feel like a kludge.