Skip to content

Latest commit

 

History

History
63 lines (42 loc) · 4.93 KB

Shaileshkumar007.md

File metadata and controls

63 lines (42 loc) · 4.93 KB

DevOps

I'm pretty sure that you've heard the word "DevOps" before. Still, you may not know what it actually means, or you are probably wondering whether DevOps is any tool or software that you need to master to become a DevOps Engineer. Don't worry at all, in this blog I'll clear all of your doubts regarding DevOps. So, let's start🚀.

Need for DevOps

Before diving deep into DevOps let's just spend some time understanding the need for DevOps. For small applications, DevOps is not necessary as you can handle everything from development to deployment by yourself but as your application starts growing and more users start using your application then you'll realize the importance of DevOps. Big companies like Amazon, Netflix, etc. use the DevOps approach as millions and billions of people are using their applications.

Basically, software development is divided into two parts. The first one is the "Development team" whose role is to design, develop and build the software while the other one is the "Operation team" which is responsible for testing, implementation, and deployment of the software. Sometimes there can be miscommunication between these two teams which results in delayed releases, system crashes, etc.

Therefore, we need some kind of methodology so that the entire process of application from development to deployment can go smoothly. That's where the concept of DevOps comes in handy.

DevOps helps in removing the communication and collaboration barriers between development and operation teams along with the fast delivery of the product hence improving customer satisfaction.

DevOps encourages faster, better, more secure delivery of the product to the end customers. It involves how quickly a product release or new feature gets into customers’ hands—all with the proper levels of quality and security. Or, it might focus on how quickly an issue or bug is identified, and then resolved and re-released.

What is DevOps?🤔

DevOps is neither a programming language nor software that you can use and master. DevOps consists of two words, Development and Operation. DevOps is actually a philosophy, tool, and practice that helps the development and operation team so that they can deliver the application and services efficiently.

Following are the benefits of DevOps:

  • Faster and better product delivery
  • Faster issue resolution and reduced complexity
  • Greater scalability, reliability, and availability
  • Automation and better security
  • Improved collaboration

Now, let's take a close look at each segment of the DevOps one by one.

DevOps Lifecycle🤩

image

As you can see that the DevOps lifecycle consists of eight phases representing the plan, code, build, test, release, deploy, operate and monitor. Here the processes on the left are the part of Development and the processes on the right are the part of the operation. As it is an infinite process hence the logo of DevOps represents infinity.

The different processes are:

  1. Plan: This phase helps define business value and requirements. Sample tools include Jira or Git to help track known issues and perform project management.

  2. Code: This phase involves software design and the creation of software code. Sample tools include GitHub, GitLab, Bitbucket, or Stash.

  3. Build: In this phase, you manage software builds and versions, and use automated tools to help compile and package code for future releases to production. You use source code repositories or package repositories that also “package” infrastructure needed for product release. Sample tools include Docker, Ansible, Puppet, Chef, Gradle, Maven, or JFrog Artifactory.

  4. Test: This phase involves continuous testing (manual or automated) to ensure optimal code quality. Sample tools include JUnit, Codeception, Selenium, Vagrant, TestNG, or BlazeMeter.

  5. Releases: In this phase, a build is ready for deployment into the production environment

  6. Deploy: This phase can include tools that help manage, coordinate, schedule, and automate product releases into production. Sample tools include Puppet, Chef, Ansible, Jenkins, Kubernetes, OpenShift, OpenStack, Docker, or Jira.

  7. Operate: This phase manages software during production. Sample tools include Ansible, Puppet, PowerShell, Chef, Salt, or Otter.

  8. Monitor: This phase involves identifying and collecting information about issues from a specific software release in production. Sample tools include New Relic, Datadog, Grafana, Wireshark, Splunk, Nagios, or Slack.

DevOps Best Practices😎

  1. Continuous Integration
  2. Continuous Delivery
  3. Microservices
  4. Infrastructures as Code
  5. Monitoring and logging
  6. Communication and Collaboration

Challenges that DevOps tries to solve🤔

  • Miscommunication and lack of collaboration
  • Conflict of interests between Development team and Operation team
  • Security
  • Application Testing
  • Manual Work