Skip to main content

DevOps - What and Why?

The very first question arises in the mind is "What is DevOps?"

Few will say it combined team of Developers and Operations. Some will say it is a person "DevOps Engineer" who works with multiple teams to get the things done in corrective manner.

Further questions comes in mind are:
  1. What is the corrective manner of doing things?
  2. How it is different from our "current" method of doing things?
  3. Do I need an extra set of tools for this?
  4. And, most important of them all, why should I use it?

Let me tell you what I've learn in my 3 days of DevOps training.

What is DevOps?
DevOps is not a team, or tool, DevOps is a culture. It is a culture for collaboration, Integration and Communication between different cross functional teams for Continuous Delivery. DevOps is not an additional team, but it is the existing team members who work together. It breaks the barrier between Infrastructure and Code at early stage.

DevOps also encourages Operations team to participate early in the Development Cycle so that products are designed to be easily deployable and maintainable.

*Image Source: Wikipedia

How can I implement DevOps culture in my project?
  • Automation Everywhere
  • No Manual Intervention
  • Use of Open Source (optional, but vary w.r.t. Application & Client)

It also ensures:
  • Collaborative Development
  • Continuous Testing
  • Continuous Release and Deployment
  • Continuous Customer Feedback and Optimization
  • Continuous Monitoring

How one can archive DevOps?
To get the maximum benefit from DevOps, one need to follow a certain path and need to implement few new process in their application development life cycle. Such as following:
  • Configuration Management
  • Continuous Integration
  • Automated Testing
  • Metrics
  • Collaboration
  • Making smart use of smart people


As soon as a change comes in to the version control tool, it will start testing the stability of the code & automated testing will start. In case of some failure, an alert will goes to the stakeholder, they will fix the issue and process will start again.

When all the test cases are successfully executed, automated deployment will get triggered and code will get deployed to production environment. Following this process with close the gap between the team located is different geographical location and there will be no time wastage.

Infrastructure monitoring and Analytics is also possible automatically.

Why DevOps?
OK, after understanding about DevOps culture, its objective, output, next question which comes to our mind is "Why should I adopt DevOps?"

In simple point after adopting DevOps culture you will get the followings:
  • Rapid Prototyping
  • Effective Support
  • Micro Services Architecture
  • API Support
  • Automation
  • Experimentation
  • Polyglot Enablement
  • Platform as a Services (PaaS)

Most of the things will be automated with DevOps (Testing, Deployment, Analytic, Monitoring etc.) you will get time to work on your Backlog and achieve more. You will be experimenting new things/tools. Dependencies of your applications can be identified at earlier stage and you don't have to waste time at the time of actual production deployment.


Achievements:
  • Code, Environment and configuration at one place
  • Automation of code release
  • Faster Release Cycle
  • Shorten and amplify all feedback loops
  • Quality - with feedback comes quality
  • Defects and performance issues fixed faster
  • Better Communication
  • More work getting done
  • Efficiency, Predictability, Reproducibility & Maintainability

Labels

Labels:

Comments

  1. venkatJuly 28, 2017 at 1:17 PM

    It's interesting that many of the bloggers to helped clarify a few things for me as well as giving.Most of ideas can be nice content.The people to give them a good shake to get your point and across the command.
    Devops Online Training

    ReplyDelete

Post a Comment

Popular posts from this blog

PowerShell: Get Actual Error

I was having hard time to find the reason why I was not able to find a custom method in a .Net DLL. Find your Assembly: PS C:\vstsagent\A1\_work\r1\a\_DevOps_CI\Scripts > [appdomain]::currentdomain . getassemblies() | Where - Object FullName - Match "MyAssembly" GAC Version Location --- ------- -------- False v4 . 0.30319 C:\vstsagent\A1\_work\r1\a\_DevOps_CI\Scripts\Tools\MyAssembly . dll PS C:\vstsagent\A1\_work\r1\a\_DevOps_CI\Scripts & gt; $ a = [appdomain]::currentdomain . getassemblies() | Where - Object FullName - Match "MyAssembly" PS C:\vstsagent\A1\_work\r1\a\_DevOps_CI\Scripts & gt; $ a GAC Version Location --- ------- -------- False v4 . 0.30319 C:\vstsagent\A1\_work\r1\a\_DevOps_CI\Scripts\Tools\MyAssembly . dll When I was trying to get the Types in the assembly, I was getting the exception: PS C:\vstsagent\A1\_work\r1\a\_DevOps_CI\Scripts > ...
Post a Comment
Read more

Notepad++ Error for 64bit - ShellExecute failed (2): Is this command correct?

Cause : It happens when you set Notepad++ to "run as" administrator on Windows 7. Fix:  To fix this, you need to manually edit the registry of your system to create a new option in pop-up menu to open files with Notepad++ Step 1 : Delete existing  Edit with Notepad++  entry from registry Go into your registry as an administrator (Run -> regedit) and search for notepad++.exe. Find the key under  HKEY_CLASSES_ROOT  that has an entry with the  Edit with Notepad++  (or maybe  Edit with &Notepad++ ) and delete the entire key. Right click and you should see that you no longer have that option. Step 2 : Create new entry Open with Notepad++ Go to: HKEY_CLASSES_ROOT\*\shell Create a new key under shell called  OpenWithNotepad  and create a subkey under that called  command . In the  OpenWithNotepad  key the default string is what you want the context menu item to be called. I set it to  Open with Not...
Post a Comment
Read more

Release approvals

Continuous Delivery is all about delivering on-demand.  But, as we discussed in the differences between release and deployment, delivery, or deployment, it's only the technical part of the Continuous Delivery process.  It's all about how you can technically install the software on an environment, but it doesn't say anything about the process that needs to be in place for a release. Release approvals don't control  how  but control  if  you want to deliver multiple times a day. Manual approvals also suit a significant need. Organizations that start with Continuous Delivery often lack a certain amount of trust. They don't dare to release without manual approval. After a while, when they find that the approval doesn't add value and the release always succeeds, the manual approval is often replaced by an automatic check. Things to consider when you're setting up a release approval are: What do we want to achieve with the approval? Is it an approval that we need...
Post a Comment
Read more