What is DevOps ? Why DevOps ? All of a sudden, How DevOps became famous and a lot of demand for DevOps. DevOps is not a technology. DevOps is not Development, QA, and Operations. There is no perfect definition for DevOps as it is evolving. As per my understanding, DevOps is a culture / fashion / trend / practice / movement / thinking. Ron Melanson, of Amazon, said that “DevOps is a lifestyle, not a title.” Some of the core principles of DevOps are:
DevOps Principles :
Automation – Automating workflows allows developers to focus solely on writing code and developing new features.
DevOps Pipeline – a loop that facilitates continuity in development
Continuous Delivery – releasing code updates frequently and fast
Continuous Integration – It encourages developers to submit their code to a central code repository multiple times a day.
Continuous Monitoring – ensures the application performs without issues.
Feedback Sharing – Developers need information from different sources to help them improve the overall quality of the app
Version Control – stay organized, focused, and up to date
A DevOps Practicer / Consultant should have knowledge and experience from development, operations, and total Software development life cycle. These people/team is responsible for all the activities of software/ an application from development to production. They make sure development life cycle goes smooth. Below are some of the concepts or practices which help to maintain DevOps Principles:
DevOps Practices :
Continuous Integration (CI).
Continuous Deployment (CD).
Continuous Delivery (CD).
Application Server Knowledge.
Automated Release Managment.
Why DevOps ?
As DevOps is more about principles and practices, it improves software delivery and increases business value.
A lot of companies are starting to build DevOps teams. The T-Shaped profiles (eg: Person who has depth knowledge in development and have knowledge also in CI and CD / a person depth knowledge and experience in operations and have knowledge in development) are ideal people for building DevOps Team.
What and Why Continuous Delivery – Explained for Beginners
What and why continuous Delivery required nowadays for the business to survive ?
Continuous Delivery is one of the important concepts of DevOps. In this article, I will try to define and keep it simple, what is Continuous Delivery and Why we need Continuous Delivery.
Below picture shows both continuous Delivery and Continuous Deployment. Generally, Based on the business requirement, key people from the organization decide when the new features or artifacts should go live to production.
What and Why Continuous Delivery ?
Creating a Repeatable, Reliable process for Release Software is Know as Continuous Delivery.
As Business perspective, Continuous Delivery helps in delivering real business value, as Quickly and Efficiently as possible.
Release often (Fast)
Release Small (Focused)
Minimum Viable Product: Test your ideas in the real world, Build better smarter Products.
Reduces Risks: smaller changes means less Risk
Continuously Deploy – Always deploying means you get much better at deployment.
The Smaller change means easy to deploy and easier to fix.
Each change is real progress, you know it’s done because you deployed it successfully.
Build Confidence – Ability to release new features, detect and fix issues.
Continuous Delivery adds a lot of value to the application. A lot of companies understood what and why continuous delivery is required in the fast pace technology world.