Manesh Mathew

Designed and implemented a highly available, scalable, and fault-tolerant CI/CD infrastructure. This included using stack GitLab as a source code repository and using Jenkins as a continuous integration and deployment tool. Deployment artifacts are Docker images. These artifacts are stored in a private container registry setup using Nexus.

Automated build trigger is achieved using GitLab webhooks. Jenkins scripted pipeline scripts were used to define the CI/CD pipeline workflow, and Jenkins pipeline scripts were maintained within the source code. Automated test execution is invoked from the Jenkins pipeline to ensure code coverage, static code analysis, and security vulnerability check.

GitLab and Jenkins notifications are enabled to send code push, and Jenkins build status notifications can be received via the Slack channel. This infrastructure is deployed in AWS cloud using CloudFormation templates, with an auto-scaling group to ensure HA.

Designed and implemented enterprise deployment architecture for a microservices application. This stack includes both Node.js and Java microservices. The application stack includes Apache Zookeeper, Apache Kafka, HashiCorp Vault, MongoDB, and PostgreSQL.

The microservices are packed as Docker images and deployed as pods in the Kubernetes cluster. The releases are specified as Helm charts and rolled out as Helm releases. Deployments in Kubernetes are segregated using namespaces in Kubernetes and with network policies. MongoDB installation is done as replica sets with a minimum of three nodes in a replica set. PostgreSQL cluster is deployed as primary and standby servers to ensure HA.

MongoDB data backup is done using AWS DLM for daily EBS snapshot. Created a custom Python script for taking point-in-time backup of PostgreSQL data directory.

Customer deployment in AWS Cloud. I was working as a DevOps engineer in setting up a customer deployment infrastructure in AWS Cloud.

This requires setting up continuous integration and continuous deployment infrastructure as well.

A Jenkins pipeline script will be invoked by a webhook trigger from GitLab when the developer code changes were merged to the upstream branch. This pipeline includes building the code, running unit tests, running security vulnerability scans, and static code analysis using SonarQube. Once the build phase is completed, Docker images will be created in the packaging stage and this image will be pushed to a Nexus repository. This image will then deployed for a continuous integration environment for running additional integration testing and to run any automated functional testing. Once this CI stage is completed, the image is promoted to the QA environment for the validation stage. Once completed, the QA will be promoted for staging and production deployments.