DEVOPS OVERVIEW
DevOps is a process framework that ensures collaboration between Development and Operations Team to deploy code to production environment faster in a repeatable and automated way. The word DevOps is an amalgamation of two words development and operations. DevOps helps to increase the speed to deliver applications and services faster. It allows organizations to serve their customers efficiently and become more competitive in the market. In simple terms, DevOps can be defined as an alignment between development and IT operations with better communication and collaboration.
Earlier to DevOps, the development and operation team worked in total isolation.
Testing and Deployment were isolated phases and were done after design and build. Hence they required more time than actual build cycles.
Without DevOps, team members are spending a large amount of their time in testing, deploying, and designing instead of focusing on the core part that is creating business services.
Manual code deployment will lead to errors in production.
DevOps Tools
DevOps is a mindset, not a tool set. But it's hard to do anything in an IT team without the right tools. In general, DevOps practitioners rely on a CI/CD pipeline, containers and cloud hosting. Tools can be open source, proprietary or supported distributions of open source technology.
Recommended by LinkedIn
How does DevOps work?
DevOps is a methodology meant to improve work throughout the software development lifecycle. You can visualize a DevOps process as an infinite loop, comprising these steps: plan, code, build, test, release, deploy, operate, monitor and -- through feedback -- plan, which resets the loop.
Ideally, DevOps means that an IT team writes software that perfectly meets user requirements, deploys without any wasted time and runs optimally on the first try. Organizations use a combination of culture and technology to pursue this goal.
To align software to expectations, developers and stakeholders communicate about the project, and developers work on small updates that go live independently of each other.
To avoid wait times, IT teams use CI/CD pipelines and other automation to move code from one step of development and deployment to another. Teams review changes immediately and can enforce policies to ensure releases meet standards.
It's easy to write software quickly; writing software that works is another story. To deploy good code to production, DevOps adherents use containers or other methods to make the software behave the same way from development through testing and into production. They deploy changes individually so that problems are traceable.
