Posts

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...
Post a Comment
Read more

Summer Open Source Project - Eclipse PDE

About the project Eclipse PDE is a development environment for creating Eclipse plug-ins and stand-alone RCP applications, enabling both contributors and enterprise developers to build custom tools. It has powered well-known applications like Xmind and KNIME, showing its versatility beyond just Eclipse IDE extensions. With a committed global user base in the tens of thousands, Eclipse PDE remains a key tool for modular, enterprise-grade application development. The Issue Eclipse PDE’s Manifest editor lacks proper UI support for the  jars.extra.classpath  attribute, causing many developers to mistakenly use  additional.bundles , which incorrectly adds compile-only dependencies as runtime dependencies. To address this, I explored the Eclipse PDE codebase and identified key files such as  BuildClasspathSection.java ,  DependencyManagementSection.java ,  pderesources.properties , and  PDEUIMessages.java . The solution involves adding a new button in the Bu...
Post a Comment
Read more

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 Gr...
Post a Comment
Read more

Bonus Assignment for Midterm Exam of Spring 2025 DevOps Class

Image
1. Tech Stack Used : Git Action, npm[Semantic Release], maven, react, springboot, docker, AWS[EC2, RDS, Route53, ECR] 2. Repository :          -Source repo : contains FrontEnd and BackEnd Code. Added release.yml so it could do tagging with Semantic Release.          -Infra repo : contains Git Action Workflow scripts. I added “Promotion.yml” script so triggered script could pull latest docker image and deploy it on RC server.  3. Work Flow :         -source repo has a workflow that releases tag in commits by semantic release         -once the release tag is created, it will kick off a promotion workflow in the infra repo         -workflow in infra repo(promotion.yml) will pull docker image and run it on pre-installed EC2         -pre-in...
Post a Comment
Read more

CICD Pipeline - Midterm Exam of Spring 2025 DevOps Class

Image
  Introduction  This project was making CICD pipeline with Git Action, Docker, EC2, RDS, ECR, and Route53. I used my side project Jake (Social Media platform for international students) as source code. The flow of CI/CD pipeline goes like below. Source Repo contains Dockerfile and Docker-Compose.yml. It needs to run locally without any error. Infra Repo contains GitAction workflow codes. This triggers launching a temporary EC2 and fetch codes from source repo. It builds docker files and conducts smoke test. If smoke test succeeds, it pushes docker image to ECR, and it is deployed in EC2 as a QA Server. Route 53 directs IP address to domain name. The Issue  There were many issues and errors while building the CI/CD pipeline.  Source Repo Local test CORS Error : Connecting FrontEnd and BackEnd caused CORS error, which is not letting other origin use same address. To fix it, I used Reverse Proxy by Nginx, and added annotation in SpringBoot controller(@CrossOrigin)....
Post a Comment
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...
Post a Comment
Read more