End To End POC To Learn DevOps & Cloud For Beginners

End To End POC To Learn DevOps

In this POC To learn DevOps, I will explain the right way to get hands-on experience on DevOps and Cloud when you don’t have a chance to work on real-time projects.

If you trying to become a DevOps engineer, learning tools and technologies definitely help you to take your DevOps journey to the next level. And with the vast amount of online learning resources and little hard work, you can learn any tool or technology.

My intention is to give you an overall idea of the entire application involved in a DevOps practice by creating CI/CD workflows and deploying an application on the AWS cloud.

In this series of guides, I will walk you through the entire CI/CD process

POC To learn DevOps & Cloud [ Project Petclinic ]

Here is the scenario we are going to assume.

A company named Scriptcamp wants to build a Pet Clinic application for its client.

The high-level requirements for the project are

  1. The application should be built on the Java Spring MVC framework.
  2. The application should be hosted on Cloud with the following.
    1. High availability.
    2. Autoscaling for applications.
    3. Highly available database.
  3. The entire build and deploy process should be automated.

Application Architecture & Approval Process

Any applications development process follows a standard set of processes from planning, development to deployments. This process differs between organizations.

For this POC, let’s assume the following process.

  1. Based on the client’s requirements, the application architect designs the application architecture.
  2. As per the client’s organizational standards, the architecture should be approved by its Enterprise architects and Enterprise security teams.
  3. As per the process, the Application architect sets up a meeting with both Enterprise architects and Enterprise security teams to explain the architecture.
  4. Finally, the architecture gets the signoff with a few suggestions from the Enterprise architect & security teams.

And the next phase is to start the development. Before

CI/CD/Infra Architecture & Approval Process

Like the application development process, CI/CD development has its own architecture and design approval process.

When it comes to infrastructure & CI/CD, In a standard organization, the following core teams are involved

  1. Enterprise security
  2. Network team
  3. Tools or Central platform team
  4. Cloud/IAM team
  5. Engineering team.

As a DevOps engineer, you will have to collaborate with the above teams in terms of infrastructure automation and CI/CD. I will talk about the involvement of these teams under each POC task.

Building CI/CD For Petclinic Application

Scriptcamp CTO wants the Petclinic team to follow all the DevOps principles for Pet Clinic application development and deployment.

So the project manager for the Petclinic application asks the team to come up with a list of high-level CI/CD tasks.

DevOps POC Tasks

Following are the high-level tasks that the team has come up with.

  1. Understanding application architecture & requirements.
  2. AWS cloud infrastructure design as per standard security practices.
  3. Setting up CI/CD infrastructure using Jenkins
  4. Setting up Artifact repository using Nexus
  5. Setting up Sonarqube for Static Code Analysis
  6. Setting up Hashicorp vault to store Secrets
  7. Setting up Prometheus for application monitoring.
  8. Branching strategy & Standard Practices for Development
  9. Creating Jenkins Pipeline for Continuous Integration
  10. Creating Pipeline for AMI creation using Packer & Ansible – The AMI contains the following
    1. AWS logging agent to push logs to cloudwatch
    2. Java code with Prometheus agent to capture application metrics.
  11. Develop Terraform Code to create Amazon RDS for the backend database.
  12. Develop Terraform code to create Route53 records.
  13. Develop Terraform code to Deploy autoscaling Group & Loadbalncer & Route 53 configurations.
  14. Jenkins Pipeline as code for Code Deployment
  15. Documenting KPIs for Infrastructure and application monitoring.
  16. Monitoring and logging dashboards for applications and infrastructure.
  17. Setting up Alerting using Prometheus for application issues.
  18. Documentation of Design, workflows, and Code.

We will use the open-source pet-clinic spring boot java application for this POC.

0 Shares:
Leave a Reply

Your email address will not be published. Required fields are marked *