DevOps Blog: What is DevOps?

What is DevOps?
DevOps culture is described by strengthened collaboration, shared responsibility, improving quality from valued feedback and increasing automation.

DevOps is a blend between Developers and Operations teams, they follow a set of processes and tools that help them to create faster and more stable applications.

The role of a Developer is to create applications that are cutting edge and easy to use. The Operations team is tasked with keeping the application as stable as possible.

What goals do DevOps hope to achieve?
Their goal is to vastly improve the workflow to satisfy the following:

  • Deployment frequency
  • Achieve quicker release times
  • Lower failure rate/ bugs of new releases
  • Shorten downtime between fixes

Background
Before DevOps, the process used was called  Waterfall and it was very different to how things are done now. Fast forward to today and it the process is known as CICD.

What is Waterfall?
Waterfall was a process where the applications used to be fully developed before being released. When the application was released, there was no solutions for fixing the bugs!

What is CICD?
CICD stands for continuous integrations and continuous development. This allows the applications to be released before being fully developed. Developers upload their code to a CI server where the code is checked to see if it compatible with the current code and ensure there will not be any clashes.

Why is DevOps important?

Build
Building is when the developers are building the desired application for the target audience.

Test
Testing is when the application goes through a rigorous testing process to check it is suitable to release to end users.

Release
The application is released after it has gone through the testing phase and it will be perceived to be suitable for end user usage.

Monitor
Here you should monitor how your application is performing and also when receiving feedback from target audience, list out what the issues are and discuss the plan on how to fix them.

Plan
With all issues gathered from the feedback, now you can address the issues, recode and test again before releasing. The diagram below shows the CICD workflow.

Leave a Reply

%d bloggers like this: