DataOps, ChatOps and More: Offshoots of the DevOps Movement
You know DevOps -- the idea that developers, admins and everyone in between should collaborate constantly on software delivery. But do you know the many offshoot movements that DevOps has helped create?
![DataOps, ChatOps and More: Offshoots of the DevOps Movement DataOps, ChatOps and More: Offshoots of the DevOps Movement](https://eu-images.contentstack.com/v3/assets/blt10e444bce2d36aa8/blt1d24deb91bd227c6/652461d428ff12e36c81d6d0/DevOps_Thinkstock_0_0.jpg?width=700&auto=webp&quality=80&disable=upscale)
DevSecOps — also known as SecDevOps, or sometimes Rugged Ops — is the art of integrating IT security operations into your software delivery workflow. By having your cybersecurity experts work alongside developers and admins as code is being written and pushed into production, you stand a better chance of finding and fixing security vulnerabilities before they are exploited by attackers — or avoiding them altogether by writing more secure code.
Do you do DevOps? Do you use the cloud? Then you're probably doing CloudOps, too. CloudOps essentially means DevOps in a cloud environment. The driving idea of CloudOps is to ensure that the admins who administer your cloud infrastructure collaborate effectively with the developers who write code for your cloud apps, the QA folks who test it and so on.
Few people get excited talking about storage. Disk arrays and scale-out file systems are things that existed deep in the recesses of your data center or cloud, and traditionally, the only people who have thought about them are the storage admins who maintain them.
But if you embrace Storage Ops, you see storage admins as part and parcel of your software delivery process. There are important advantages to be gained from Storage Ops because when storage admins are plugged into software delivery, your organization has a much better chance of ensuring that its apps and services have the storage resources they need to run. Without Storage Ops, you can end up with developers who don't fully understand storage requirements and availability, leading to serious problems down the line.
If developers and admins can produce better software by collaborating constantly, can't data scientists also work more efficiently by integrating more directly with other teams — like programmers and storage admins — who play important roles in facilitating data analytics? That's the idea behind the DataOps movement.
Network admins are not always part of the DevOps conversation. But advocates of NetOps want them to be. In a NetOps world, the planning, setup and maintenance of computer networks go hand-in-hand with software delivery — which makes sense, after all, since you can't very well produce software if you don't have a reliable network.
The holy grail of the DevOps movement, in a sense, is NoOps — which means that, well, you have no need for manual IT Ops workflows of any kind. NoOps promises to make infrastructure essentially maintenance-free — just like vinyl siding (OK, maybe we're reaching with that analogy, but the core idea of requiring zero maintenance is there).
The idea behind NoOps is that, by taking full advantage of DevOps tools and processes like scripted infrastructure and automated configuration management, it can become possible to build environments that are entirely self-configured, self-scaled and self-managed. True NoOps has not yet arrived, but as DevOps tools become ever more sophisticated, NoOps is on the horizon.
ChatOps (which, unlike most of the other *Ops in this gallery, is a specific use of technology rather than a concept) is the idea that you can use communication tools — like Slack and HipChat — to automate more of your DevOps workflows. For example, you could set up a chat bot that automatically notifies your team when there is a problem in your infrastructure — and you could even allow the team to issue commands to the chat bot to resolve the problem directly from your communication platform. In this way, ChatOps streamlines workflows and maximizes communication.
ChatOps (which, unlike most of the other *Ops in this gallery, is a specific use of technology rather than a concept) is the idea that you can use communication tools — like Slack and HipChat — to automate more of your DevOps workflows. For example, you could set up a chat bot that automatically notifies your team when there is a problem in your infrastructure — and you could even allow the team to issue commands to the chat bot to resolve the problem directly from your communication platform. In this way, ChatOps streamlines workflows and maximizes communication.
You know DevOps — the idea that developers, admins and everyone in between should collaborate constantly on software delivery. But do you know the many offshoot movements that DevOps has helped create? Here's a look at Ops movements that apply DevOps principles to other contexts — from ChatOps and CloudOps to DevSecOps.
About the Author(s)
You May Also Like