Oct 31, 2022
DevOps Tools are Bloatware!
Disclaimer — It is my personal opinion and view.
I started my career as a junior DevOps(2016) and currently working as a DevOps Architect. I have seen the below-mentioned tools grow from being helpful to bloatware.
Let me try to explain this with examples
1. In 2016, I started as Junior DevOps and started learning Jenkins to build and deploy things.
Now(2022), we have Jenkins, Bamboo, Gitlab, Teamcity, Circle CI, Bazel, FluxCD, ArgoCD, GitHub Actions, AWS CodePipelines, Azure DevOps, GCP Deployment Manager, Harness, Bash Scripts, and many more.
None of those mentioned above tools inter-compatible with each other and the worse part is that they have mind-boggling different schemas/terminology/technology/etc.
2. In 2016, I was working aka learning on Kubernetes, I spent several months trying to understand the basics of it. I was using kubectl and doing pretty well at the job as well (my evaluation). Now fast forward to 2022 aka Now, we have Kubernetes, Rancher, Mirantis Kubernetes, VMware Tanzu, RedHat Openshift, DC-OS, Canonical Kubernetes, AKS, EKS, GKE, and many more.
And again, none of those mentioned above tools inter-compatible with each other and the worse part is that they have mind-boggling different schemas/terminology/technology/etc.
3. Let’s talk about Monitoring, I started with Nagios as the primary monitoring tool in 2016 because it was great and had a hell lot of plugins for each and everything. Then comes Icinga, Icinga 2, Prometheus, Zabbix, Thanos, InfluxDB, Open Metrics, NewRelic, Datadog, Victoria Metrics, SignalFx, and many more.
And again, none of those mentioned above tools inter-compatible with each other and the worse part is that they have mind-boggling different schemas/terminology/technology/etc.
So what is the solution?
IMHO, we can follow the three R’s principle aka Reduce, Reuse and Recycle.
Finally, if you want to be DevOps, here is a small list of tools you would need to learn → https://landscape.cncf.io
