2025 Spring CS686 DevOps - Final Project

 Final Project Overview

-make MSA service

-use EKS

-Automate

-deploy blue-green strategy 

-deployment flow : Nightly Build -> QA -> UAT -> Prod 


Steps

1. Make MSA codes 

Dismantled existing code into three services - backend1, backend2, and frontend

2. By Git Action test and deploy

Made GitAction Workflow('Nightly-Build') to start temporary EC2 and test(smoke-test) the code. Used dockers to run three different services and tested if it works.

3. Deploy to QA Server

Using GitAction, deployed it on QA server(single EC2 server). Now we can see it at IP address of EC2 instance. 


4. Make EKS Cluster and Deploy Blue Service of UAT 

Make VPC and EKS Cluster. 
Make Node Group. Need to use good enough instance. 
Using Git Action and yaml file from Infra repo, apply configuration to running pods on EKS. 
Now your microservice is deployed on EKS and you can access it through url. 

5. Switch it to Green Service of UAT 

Deployment of Green will fetch new docker image and Service will serve it.
By changing selector, you can change Blue to Green.

6. Make Prod Server 

Do the same thing as UAT Server, but add url through DNS(Route53) this time.

Tech Stack Used

React.js, SpringBoot, Docker, Nginx  
Git Action, Github
AWS RDS, ECR, EC2, EKS, CloudFormation, Route53 
ArgoCD



Comments

Post a Comment

Popular posts from this blog

Headquarters SWE Internship

Nov 24 - Nov 30 :  Designed the messaging/chat database schema Implemented 2-way SMS using AWS SNS + Lambda and saved inbound messages to the database. Built outbound SMS delivery logging using CloudWatch Logs Subscription Filters + Lambda → sent results to our server. Designed the frontend chat UI (iMessage style) and implemented message list/detail/compose pages. Implemented routing logic for patient SMS replies depending on available support team members. Added real-time chat using SSE and completed end-to-end chat flow. Nov 17 - Nov 23: Implemented ghost preview for rehab templates and refactored related APIs. Rebuilt the z-index system with Matan to unify multiple conflicting layers. Added small UX improvements (email/phone input on patient creation, map UI for in-person appointments, timeline fixes). Fixed multiple bugs and improved consistency across the interface. Participated in bug-hunting and tested login + PWA features. Nov 9 - Nov 16 :  Added edit functionality on...
Read more

Open Source Project - Open Energy Dashboard

Image
  Open Source Project - Open Energy Dashboard Introduction  During last 4 weeks our CTI team (Hyunoh, Abas, Ezequiel, and Mon) worked on Open Energy Dashboard open-source project. Open Energy Dashboard(OED) is a project where it is used as an energy dashboard so that all the users can manage the energy usage of their worksite. ( link ) The Issue  We as a team coded a line group reading test case(c11) in JavaScript and TypeScript using Docker and Visual Studio Code, ensuring values are read correctly to reflect 14 days giving hourly point and middle readings. ( Link )   Test cases are important to enhance accuracy of a software. By writing and updating test case, we estimate we improved test coverage by 30% and enhanced data accuracy by 25% in a Dockerized environment, ensuring seamless integration and reliable energy value processing.  To resolve the issue, our team 1. looked up for development document,  2.starting Docker and activate web and database...
Read more