Have you ever wondered why can’t you get one definition of DevOps? Wikipedia definition says “DevOps is a set of practices that combines software development (Dev) and IT operations (Ops). It aims to shorten the systems development life cycle and provide continuous delivery with high software quality. DevOps is complementary with Agile software development; several DevOps aspects came from Agile methodology.”
Amazon defines DevOps as “DevOps is the combination of cultural philosophies, practices, and tools that increases an organization’s ability to deliver applications and services at high velocity: evolving and improving products at a faster pace than organizations using traditional software development and infrastructure management processes.”
Azure defines DevOps as “A compound of development (Dev) and operations (Ops), DevOps is the union of people, process, and technology to continually provide value to customers.”
Atlassian defines DevOps as “DevOps is a set of practices that works to automate and integrate the processes between software development and IT teams, so they can build, test, and release software faster and more reliably.”
It is for sure that every company has its own way of looking at DevOps. If you are a team member DevOps is a way of breaking silos between not just Development and IT operations, but also quality engineering and security. DevOps helps all these functions to coordinate and collaborate in a way that they produce superior and more reliable products. DevOps is not about tools, automation, practices but also culture which enhances the team’s ability to better respond to what customer needs several folds. It also allows them to build applications which helps the business achieve their goals faster, and delight the community with stress free usage of secure applications.
If one does a survey on number of times keyboards were hammered because either the websites would take forever to load or had bugs, we can conclude that this frustration has touched most of the netizens. Imagine a world where issues are fixed as soon as they pop up resulting in reducing the number of broken keyboards. That is what DevOps can give us — a world with a little more calmness in it.
History of DevOps
Scaled Agile Framework (SAFe®) defines DevOps as a mindset, a culture, and a set of technical practices. It provides communication, integration, automation, and close cooperation among all the people needed to plan, develop, test, deploy, release, and maintain a Solution. The goal as per Scaled Agile is simple: deliver value whenever there is business demand. This is indeed achievable, as “high-performing IT organizations deploy 30x more frequently with 200x shorter lead times. … 60x fewer failures and recover 168x faster.”
The history of DevOps if often not known. Very few people are aware that it is a movement which found its feet through a movement on Twitter. Let’s see what led to #DevOps movement which changed the IT world for good.
The DevOps movement started in June 2009 at O’Reilly Velocity Conference, San Jose, CA where John Allspaw & Paul Hammond presented “10+ Deploys Per Day: Dev and Ops Cooperation at Flickr”. You can experience the historic moment by watching the clip here https://tech-talks.code-maven.com/ten-plus-deploys-per-day.html
From there it was taken forward by Patrick Debois in October 2009, Ghent, Belgium – First DevOpsDays Conference simply because he missed the velocity conference.
This was an inflexion point for DevOps movement. Post the conference the conversation continued on Twitter with #DevOps and that led to the inception of global DevOps movement. More and more of DevOpsDays, meetups, blogs, videos, sharing thoughts and experiences was seen in the industry. New Tools Emerged like Puppet, Chef, RunDeck, JuJu.
In March 2011 Gartner predicted Enterprise Adoption which became a reality. In 2012 – 14 various vendors flooded in and made it mainstream.
DevOps is a community-oriented, grassroots movement by agile community. The seed of all this idea was in Patrick Debois’s vision and need of “Agile infrastructure.” DevOps is growing because its need of the hour. This is our time to contribute in shaping how the future DevOps looks like. We are in a unique situation where we are the consumers as well as developers. To know more about DevOps Fundamentals you can join us on our DevOps Course.
Flavors of DevOps
The advent of DevOps brought in flurry of definitions for it. People called it a culture shift, some said it is all about tooling and automation, some thought it will make them lightning fast when they take their solutions to customers. Well it’s all of the above and more. As Scaled Agile Says, DevOps is a combination of two words, development and operations. Without a DevOps approach, there’s often significant tension between those who create new features and those who maintain the stability of the solution in production. DevOps ends the silo approach, providing an enterprise with the ability to develop, deploy, and release small batches of functionality to the business or customer in a flow process called the continuous delivery pipeline. It includes not just development and operations, but everyone needed to release value, such as security, compliance, audit, marketing, legal and others.
Following are some of our favorite ones:
DevSecOps: The full form of DevSecOps is very simple, its Development, security and Operations. The modern customer demands speedy solutions with security. We can no longer afford the siloed approach of specialized traditional security teams who make the security compliance alibi to the lethargic delivery. We need a cultural shift to imbibe security into the rapid-release cycles that are typical of modern application development and deployment, also known as the DevOps movement. The organizations need to embrace shift-left mentality to bridge the gap that usually exists between development and security teams to the point where many of the security processes are automated and handled by the development team itself, and that’s DevSecOps for us.
BizDevOps: BizDevOps focuses on breaking the boundaries between business, development and Operations. Sometimes just BizOps is used to represent the concept the same concept where the business teams with in the organization work directly with their IT counterparts increasing the probability of a solution which is easy to maintain, develop and use.
ArchOps: ArchOps focuses on breaking the silo between how IT software is architected and operations. ArchOps is about laying the foundation almost minimum needed environment for everyone to work efficiently.
The focus of all of these approaches is to improve communication and breaking silos between various areas. Generically the work DevOps has become the most commonly used for all of the above. It’s creates a culture and world where Development, Operations, Business, Compliance, Architecture and Security works together in a seamless way to enable exponentially fast delivery of solutions to customers. If you want to learn more about DevOps Join us one of the courses below and see what works best for your organization.
What’s Next on Your DevOps Journey?
Have a look at our DevOps Courses: