So what exactly is DevOps? Let's take a small hypothetical example to illustrate. Let us say there's a small startup that assembles AI-enabled cleaning robots. There are 3 programmers (let's be lazy and simply call them Team D) who compose and execute the code to produce the robots and 2 operational people (Team O of course) who maintain the robot infrastructure in the real-world environment and supply aid for the robot consumers.
Team D has only spent 8 months producing the latest robot. It can recognize individuals, take orders from Alexa devices, and clean like a boss. Team D has spent time producing this robot into their controlled dev environment and everything seems to be working smoothly. They couldn't be prouder.
They hand over their production to Team O that immediately takes it out to the real world. That's when the problems start. It turns out that the perfect cleaning robot isn't so perfect after all. It does not recognize everybody, it can follow Alexa commands breaks down when they're given by various people and it can't reach and vacuum tricky shelves.
Team O is frustrated and angry. They've been awaiting this robot to get long and they can't think it's an unmitigated catastrophe. They think that everything was functioning perfectly through controlled testing conditions and the royal mess now needs to be because of Team O's poor implementation.
In conclusion, there is sub-optimal merchandise in the current market, it feels like improvements and corrections will now take almost as long as merchandise roll-out failed, and two quite competent teams now despise each other and their tasks.
In short, this is why DevOps was established and why more than 70 percent of SMBs (Small and Medium Businesses) were adopting DevOps Services in their companies in 2016. A whole lot of heartache, frustration, and inefficiency might have been avoided had Team D and Team O functioned with every other directly from conception and execution to support and delivery.
Team O had no involvement when the code was being written and the robot was being built while Team D was entirely out of the image when the robot went out to real life and cleaned many unique houses. The result was a robot that was not ready for the market and a dev team that still doesn't know how to fix things.
As you can imagine, a lot of time will go-ahead before the robot is finally market-ready. There will be several iterations as Team D creates some adjustments and Team O sends the robot out to the actual world. And not only during product development, but the same issue will also last if the robot requires maintenance and updates. As a result, even a small startup ends up becoming ineffective and slow and there's a fantastic chance it falls out to other businesses that get superior products to market faster.
This was the issue that companies began seeing particularly as technology became more sophisticated. Keeping their operations and development groups isolated from each other was resulting in slower delivery and not as efficient services and products. Moreover, many processes in the company operations that could have been readily automated to increase efficiency were not being automated because the developers were simply unaware of these.
That is when the idea of DevOps came to the fore and began being adopted broadly. DevOps is only a pair of philosophies, practices, and resources that help an organization to produce better products faster by easing the integration of the development and operations functions. This permits companies such as the person in our example to serve their clients and markets in a better way and also have a competitive advantage.
Read more on DevOps:
https://www.testingxperts.com/blog/what-is-devops
https://serenagray2451.wixsite.com/website/post/what-is-devops-the-ultimate-guide-to-devops
Comments
Post a Comment