3 ms·
Compare https://www.stackalytics.io/?metric=commits&release=folsom https://www.stackalytics.io/?metric=commits&release=folsom from 10 years ago with https://www
by cmsj 4y ago
Compare https://www.stackalytics.io/?metric=commits&release=folsom https://www.stackalytics.io/?metric=commits&release=folsom from 10 years ago with https://www.stackalytics.io/?metric=commits&release=zed https://www.stackalytics.io/?metric=commits&release=zed from this month. Notice that 2012's Folsom release was mostly made by OpenStack providers while 2022's Zed release was mostly made by Red Hat and OpenStack consumers.
(might help to expand to "All").
OpenStack did find some markets, enough to sustain a couple of vendors, but it didn't replace AWS, but it's also not trying to replace AWS anymore, it's trying to continue to serve the users it did find.
Shifting more towards my personal opinion: Containers are, in most cases, a more sensible unit of software deployment than VMs are, so OpenStack was always going to "lose" to something built around containers.
Shifting more towards other peoples' opinions: Severless is, in most cases, a more sensible unit of software deployment than containers are, so k8s will either be supplanted or become uninteresting infrastructure at some point.
- z33k 4y agoWhat is a serverless deployment unit? We already have Fargate, so no need to choose between serverless and k8s.
- vbezhenar 4y agoI don't understand why containers are not serverless deployment unit. Run container, send http request to it, shutdown if necessary.
- cmsj 4y agoI'll start by repeating that the serverless part of my comment was me extending the things that other people are predicting for the future. I'm not 100% I agree, but I'll continue their position: containers are only really better than VMs because they use fewer resources. They are not better than VMs in that you still have a whole software stack inside them that you have to care about. Anyone building their own containers should also be maintaining a whole pipeline for updating all of the software in the containers that isn't their application. Narrowing the unit of software deployment down to the application itself, removes a lot of that (or rather abstracts it to whomever is responsible for maintaining the serverless runtime containers you use).