![\"\"](\"https:\/\/blog.cloudxlab.com\/wp-content\/uploads\/2021\/09\/Screenshot-2021-09-10-at-9.33.26-AM.png\")
<\/figure>\n\n\n\nBenefits of DevOps<\/p>\n\n\n\n
![\"\"](\"https:\/\/blog.cloudxlab.com\/wp-content\/uploads\/2021\/09\/Screenshot-2021-09-11-at-6.22.43-PM.png\")
Benefits of DevOps<\/figcaption><\/figure><\/div>\n\n\n\n\n\n\n\n
- Rapid Delivery<\/strong>
Increase the frequency and pace of releases so you can innovate and improve your product faster.<\/li>- Reliability<\/strong>
Ensure application updates and infrastructure changes so you can deliver at a more rapid pace.<\/li>- Scale<\/strong>
Operate and manage your infrastructure and development processes at scale.<\/li>- Speed<\/strong>
Innovate for customers faster, adapt to changing markets better, and grow more efficient<\/li>- Better Collaboration<\/strong>
Build more effective teams under a DevOps cultural model, which emphasizes values such as ownership and accountability.<\/li>- Security<\/strong>
Move quickly while retaining control and preserving compliance.<\/li><\/ol>\n\n\n\nUnderstanding DevOps<\/p>\n\n\n\n
![\"Tools](\"https:\/\/blog.cloudxlab.com\/wp-content\/uploads\/2021\/09\/Screenshot-2021-09-10-at-9.53.29-AM.png\")
Tools used in DevOps<\/figcaption><\/figure>\n\n\n\n DevOps stands for:
1. Development and
2. Operations<\/p>\n\n\n\nThere are 8 phases in DevOps as follows:<\/p>\n\n\n\n
1<\/strong>. Plan<\/strong>
The planning phase involves a shorter goal planning. A scrum or agile planning is a better choice. The various tools you use are:
1. Microsoft Office, Google Docs \/ Sheet
2. Project Management Tools – Microsoft Project
3. Task Management tools – Asana, Jira, Mantis<\/p>\n\n\n\n2. Code<\/strong>
Text editors and Integrated Development Environments
1. VS Code, Vim, Emacs
2. Eclipse, XCode, Visual Studio
Source Code Management (SCM) Tools
1. Git – Best Choice, Older: SVN, CVS
2. Server – GitLab, GitHub, or own
Unit Test Case Libraries – depends on the language
1. Selenium, JUnit<\/p>\n\n\n\n3. Build<\/strong>
Build process involves compiling code, copying the assets, generating config and documentation. It should work on the developer machine as well as on the unattended machine.
There are various build tools:
Maven, Ant, SBT, etc<\/p>\n\n\n\n4. Test<\/strong>
Testing involves verifying if the code is performing as per requirement. Unit Testing starts at coding time. Write test cases before you code.<\/strong>
Various types of testing are:
Manual testing, Unit testing, Integration testing, Stress testing<\/em><\/strong>
Tools: xUnit, Selenium, Scripts<\/em><\/strong>
To ensure completeness, we use code coverage tools like Cobertura<\/em><\/strong>.<\/p>\n\n\n\n5. Release<\/strong>
Once the testing has been successfully done, the build is released as RC<\/em><\/strong> (release candidate) which is ready for being deployed in production.
Tools like Jenkins<\/em><\/strong> are used for release. Also, Apache Maven repositories<\/em><\/strong> are also used for releasing the binaries.<\/p>\n\n\n\n6. Deploy<\/strong>
Once the release is finalized, we can deploy it using different automation tools: Puppet, Chef, Ansible, SaltStack<\/em><\/strong>
Newer tools such as Docker<\/em><\/strong> and Kubernetes<\/em><\/strong> help scale infinitely and instantaneously.
Docker and Kubernetes are used in testing also these days in Continuous Integration.<\/p>\n\n\n\n7. Operate<\/strong>
Once the software is in production, users can use it and the product managers can customize it. During the operating phase, we can measure the effectiveness using A\/B Testing<\/em><\/strong>.<\/p>\n\n\n\n8. Monitor<\/strong>
We also need to monitor the various system resource consumptions such as Nagios.
We must also monitor the various logs and errors being thrown by the system. See: Apache Logging System<\/a>
Visualization tools such as Grafana<\/em><\/strong> are used to represent metrics.<\/p>\n\n\n\nDevOps Practices<\/p>\n\n\n\n
![\"\"](\"https:\/\/blog.cloudxlab.com\/wp-content\/uploads\/2021\/09\/Screenshot-2021-09-11-at-6.30.17-PM.png\")
DevOps Practices<\/figcaption><\/figure><\/div>\n\n\n\n Continuos Integration<\/strong>
It refers to the build and unit testing stages of the software release process. Every code commit triggers an automatic workflow that builds the code and tests the code. It helps in finding and addressing bugs quicker.<\/p>\n\n\n\nContinuous Delivery<\/strong>
It automates the entire software release process. Continuous Delivery extends the Continuous Integration.
Every code-commit triggers an automatic workflow that builds the code (Continuous Integration). Tests the code and (Continuous Integration). Then deploys the code to staging and then to production.<\/p>\n\n\n\nMicroservices<\/strong>
Design single application as a set of small services. Each service runs its own process. Each service communicates with other services through a lightweight mechanism like REST APIs. Microservices are built around business capabilities. Each service caters to a single business purpose.<\/p>\n\n\n\nInfrastructure as Code<\/strong>
Infrastructure is provisioned and managed using Code and Software development techniques such as Version control and Continuous integration. This helps developers and system admins to manage infrastructure at scale. Without worrying about manually setting up and configuring the servers and resources.<\/p>\n\n\n\n - Reliability<\/strong>