"If you force developers to learn Helm, Kustomize, or how Kubernetes manifests work, you are wasting their time. Give them environments instead. If you look at the Cloud Native Computing Foundation landscape it might seem cloud developers are a lucky bunch. There seems to be an existing tool for literally every part of the software development life cycle. This means that developers can focus on what they want (i.e., creating features) while everything else (e.g., continuous integration and deployment) is already in place. Right?"
"Not so fast. The CNCF landscape tells only part of the story. If you look at the cloud tools available, you might think that everything is covered and we actually have more tools than needed. The problem, however, is that the cloud ecosystem right now has the wrong focus. Most of the tools available are destined for administrators and operators instead of feature developers. This creates a paradox where the more tools your organization adopts, the less happy are your developers. Can we avoid this?"
"Looking beyond the clusters It was only natural that the first cloud tools would be about creating infrastructure. After all, you need a place to run your application, in order to offer value to your end users. The clear winner in the cloud ecosystem is Kubernetes, and many tools revolve around it. Most of these tools only deal with the cluster itself. You can find great tools today that Create Kubernetes clusters Monitor Kubernetes clusters Debug Kubernetes clusters Network and secure Kubernetes clusters"
Cloud-native tooling often creates the impression of comprehensive development lifecycle support while focusing on infrastructure and clusters. Many tools target administrators and operators rather than feature developers. Developers prioritize shipping features and view Kubernetes as an implementation detail similar to virtual machines. The operator-centric tool focus covers cluster creation, monitoring, debugging, networking, security, autoscaling, and cost optimization. Increased tool adoption can produce tool sprawl and reduce developer happiness. Forcing developers to master Helm, Kustomize, or manifest internals diverts time from feature work. Providing ready environments preserves developer productivity and reduces platform complexity.
Read at InfoWorld
Unable to calculate read time
Collection
[
|
...
]