The beauty is that you cannot over-architect your homelab (within your budget limits, of course!). A lab is a playground where you can safely run experiments, break things, learn and grow. □□Even if you can abstract away some of this for your developers, some folks will have to understand things like k8s networking.Ī homelab is the perfect environment to run Kubernetes. □ Your developers will have to spend time learning and understanding Kubernetes □You will need to invest in dedicated people with the right skills #4 You have the people, money, time and resources to run Kubernetes However, there might be circumstances where your specific use case won't work, and you need more control.Īgain, folks in this category usually have significant resources. These are enough for most organisations to adopt microservices without Kubernetes. If you need to embrace this architectural style, then Kubernetes could be a good choice.Ĭloud providers already provide good building blocks for hosting microservices without needing to run Kubernetes. #3 You are transitioning to microservices or have a specific use caseįirst, I hope you have thought through why you are using microservices. Some organisations have to run their applications in their own data centers on-premise due to cost, regulatory or security reasons, you are likely to tick the box for point #4. #2 You have to run on-premises and in the cloud: But unfortunately, I would say that it is usually part of the premature optimisation trap.įocus on what your users need first - do they need you to remove vendor lock-in or be multi-cloud? Vendor lock-in is one of those things that folks talk about a lot and try to avoid. It has an active community, a huge ecosystem and the Kubernetes APIs are becoming an unofficial open standard.Ĭompanies with these use cases are in a niche and are massive companies with a lot of resources see point #4. Kubernetes is a great open source solution to avoid vendor lock-in as it allows you to run your applications in multiple locations. #1 You are concerned about vendor lock-in or need to run multi-cloud That said, some organisations could and perhaps even should use Kubernetes. So when should you use Kubernetes? Here are five reasons you might consider using Kubernetes.Īs I said last week, I think many folks can save their companies a lot of time and money by avoiding Kubernetes. It was the top item for most of the day and provoked a storm of comments. I didn't expect last week's post about Kubernetes to blow up on Hacker News.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |