Just when I was scrolling through my official mail on reading eBooks, I happened to see a book suggestion on “Dive into the core of DevOps strategies “ by Sricharan Vadapalli. Lately,the word “DevOps “is creating buzz in the IT industry .Though I knew about DevOps in bits and pieces ,I did not have a profound knowledge about it . For this reason, I wanted to read the book. And ,yes, as it’s evident from the name, the book sheds light on DevOps and its strategies.
What’s in it for you?
So, if you haven’t read or known about DevOps earlier, you can get to know the history of devOps, what is it all about ,the roles and responsibilities of an DevOps engineer and how DevOps has been creating changes in the industry .
History is as important as the topic .So, let’s get to know,
How DevOps happened?
This is a long story short .So, the protagonist of this story goes by the name Patrick Debois ,a frustrated Belgian. He worked as a tester on large data center migration and was highly annoyed with the project because of constant switching back and forth between development and the silo of operations. Adding to his woes, was the separation and lack of cohesion between application methods and infrastructure methods .He knew that he wanted to bridge this wide gap.
Later, in an agile conference that was held in Canada, he came across a like-minded person named Andrew .They, together formed a discussion group to post ideas about solving this huge divide on development and operations. He ,then happened to watch a presentation about “10+ Deploys a Day: Dev and Ops Cooperation at Flickr “which was exactly what he was looking for .In 2008,he called upon a meeting to discuss the pros and cons of DevOps .His positive outlook on its impact on the industry lead to more attention for the DevOps movement, and it wasn’t long before many IT industries began to adopt these new practices. DevOps actually became a thing!
Why was Patrick amazed by DevOps ?
DevOps ,in short is to develop, deploy, and improve software throughout the lifecycle of the product or service. There are common problems that we face in the software industry which can be cut to three major ones .
1. The business tends to be tremendously afraid of change and the painfully long time to bring in new features .
2.The lack of confidence on our own work products .The inevitable questions we ask ourselves , “Will the code behave as expected?”
3.A problem manifests itself when its on site from nowhere and the tendency of the developer to retort saying ,”it did work on my machine “.
4. Problems are passed between business analysts, developers, QA specialists and sysadmins leading to an “us and them “mentality where we are consciously suspicious of each other.
Now Patrick and team were able to bring in an open statement that DevOps could solve these problems in a better way!
They found out that just like everywhere “communication “was the major problem. So, they jotted a set of practices that promote communication and collaboration among teams like development, quality assurance, and IT operations. They wanted them to work hand-in hand, just like the below picture.
Teams develop best practices and principles that will make development cycles shorter and assist teams in continuously delivering high-quality software. Now,
What are the principles ?
- Automate processes.
- Continuously deliver high-quality systems.
- React quickly to feedback to continuously improve processes.
Sounds like agile ,right ?Yes ,DevOps is actually an extension of agile which addresses the lack of communication between the development and operations . You must be curious to know how a DevOps engineer works in versatility .Let’s get to know the,
Roles of a DevOps engineer
1.He /she manages the IT infrastructure that supports software code in dedicated, Multi-tenant or hybrid cloud environments.
2. Tasks might include test data preparation, results analysis, and problem troubleshooting and issue communication back to the software developers.
3.They might have to provision resources, select an appropriate deployment model, direct testing protocol to validate each release and monitor performance after release.
4.They must understand the basics of software development languages and be familiar with the development tools used to create new code or update existing code.
6.A DevOps engineer focuses on automation and maintenance in the live environment. For example, a DevOps engineer would automate and maintain a big data build pipeline; perform on-call service for the system availability; develop or source application and system management tools that mitigate manual effort; implement automated management features.
DevOps in automotive ?
Yes ,once you have mastered all these roles ,you can call yourselves “DevOps complete !”An interesting fact is that DevOps has now been making rounds in the automotive industry too .
Due to the increasing demand for advanced features, more than autonomous/self-driving, driving assistance, or automated parking. We know that all of them have even come into existence . You leave your car in the parking lot, hitting a button on your phone, and the car parks itself, isn’t that cool? You need DevOps principles here? Of course, Yes.
“DevOps is not a goal, but a never-ending process of continual improvement.”
Furthermore, there are many topics and information about DevOps that has to be explored and discussed.I hope to read the entire book and summarize them into different topics going forward .Hoping that this basic blog about DevOps was informatory.