Skip to main content

DevOps

DevOps is a set of practices that combines software development (Dev) and IT operations (Ops).

It aims to shorten the systems development life cycle and provide continuous delivery with high software quality.

Building on Agile and Lean, DevOps enables the business to respond to changes and meet customer needs faster.


DevOps process:

  1. Coding – code development and review, source code management tools, code merging.
  2. Building – continuous integration tools, build status.
  3. Testing – continuous testing tools that provide quick and timely feedback on business risks.
  4. Packaging – artifact repository, application pre-deployment staging.
  5. Releasing – change management, release approvals, release automation.
  6. Configuring – infrastructure configuration and management, infrastructure as code tools.
  7. Monitoring – applications performance monitoring, end-user experience.

Benefits of DevOps:

  1. Faster time to market
  2. Higher ROI
  3. Greater user/customer satisfaction
  4. Increased efficiency
  5. Improved collaboration
  6. Early detection and correction of issues

CI/CD is a method to frequently deliver apps to customers by introducing automation into the stages of app development.

The main concepts attributed to CI/CD are continuous integration, continuous delivery, and continuous deployment.

CI/CD is a solution to the problems integrating new code can cause for development and operations teams.

Specifically, CI/CD introduces ongoing automation and continuous monitoring throughout the lifecycle of apps, from integration and testing phases to delivery and deployment.

Taken together, these connected practices are often referred to as a "CI/CD pipeline" and are supported by development and operations teams working together in an agile way with a DevOps.

Tools used:

Git (Coding Phase):  tool used for source code management.

Maven (Build Phase): dynamically downloads Java libraries and Maven plug-ins from one or more repositories and create build.

JUnit (Test Phase):  used to write and run repeatable automated tests

Jenkins (Release Phase): central build and continuous integration

Docker (Deploy Phase): enables developers to package applications into containers, configure containers ready to deploy to the cloud.

Kubernetes (Operate Phase): Kubernetes is a system that manages containers (containerized applications) where a container could be explained as a lightweight virtual machine. To build an application you need to build a bunch of containers and then use Kubernetes to manage those containers.

AWS Cloud Watch (Monitor Phase): collects monitoring and operational data in the form of logs, metrics, and events.


Comments

Post a Comment

Popular posts from this blog

Scaled Agile Framework (SAFe)

The Scaled Agile Framework (SAFe) is a set of organizational and workflow patterns for implementing agile practices at an enterprise scale. The framework is a body of knowledge that includes structured guidance on roles and responsibilities, how to plan and manage the work, and values to uphold. Scrum is a simple, flexible approach to adopting Agile that's great for small teams. SAFe is an enterprise-wide Agile framework designed to help bring Agile beyond the team and into the company as a whole. Scaled Agile has built a comprehensive level that includes all the four layers called the team, program, large solutions, and portfolio level. 4 Layers: Portfolio - Strategy, Vision, Roadmap, Strategy goal, Decision making, Budget, Portfolio level metrics,  Program - Align multiple teams towards a common mission, Bring together all the Agile teams, transparency, collaboration, and synchronisation, Scrum of Scrums, Product Owners to define the overall vision. Large Solutions - archite
Post a Comment
Read more

Risk Register

A project risk register is a tool project managers use to track and monitor any risks that might impact their projects. Risk management is a vital component of project management because it's how you proactively combat potential problems or setbacks. Risk Description Impact Risk Response Risk Level Risk Owner Automation Testing Software licence delay Delay in starting testing and project schedule impact As we have one licence. Planned to start automation testing in 2 shifts. Planned to get one more licence in 2 weeks’ time. High IT team Frequent Disruption in dependency API services Delay in development of integration and unit testing Dependency API service is down, and the team is working on resolving the issue. Continuously working with API team High External Team/ Project Manager There is chance of new requir
Post a Comment
Read more

Lessons learned from sprint retrospective meeting

Scenario: Team Missed Sprint Goals Challenge: A development team consistently missed its sprint goals, leading to frustration and a drop in morale. Team members felt overwhelmed by the workload and struggled to communicate effectively. Retrospective Insights: During the retrospective, team members openly discussed their challenges and frustrations. They identified bottlenecks in communication, unclear priorities, and unrealistic expectations. The team realized that individual workloads were not evenly distributed, causing burnout for some members. Lessons Learned: Effective Communication Matters: The team recognized the importance of clear communication. They committed to regular stand-up meetings, where everyone shared progress, blockers, and priorities. Balancing Workloads: The retrospective highlighted the need to distribute tasks more evenly. They decided to monitor workloads and adjust assignments accordingly. Setting Realistic Goals: The team acknowledged that setting achievable
Post a Comment
Read more