Location Research Breakthrough Possible @S-Logix pro@slogix.in

Office Address

Social List

Zero-Downtime Release Automation for a High-Availability E-Commerce Application

Description

This project creates an automated deployment system for an e-commerce application that allows software updates without stopping the website. When a new version is ready, the system creates a second environment, tests the new version, and gradually moves customer traffic to it. Spinnaker manages the release, while Envoy Proxy controls traffic between the old and new versions. If the new version causes errors or performance problems, the system automatically sends traffic back to the stable version. The main goal is to provide zero-downtime releases, safe deployments, automatic rollback, and continuous availability for the e-commerce application.

Aim

To design and implement a highly reliable, zero-downtime release automation pipeline using GitHub Actions, Spinnaker, and Envoy Proxy on Cloud to manage safe deployments, canary releases, and automatic rollback.

Objectives

01 Automate application build, testing, and deployment.
02 Use blue-green and canary deployment strategies for safer releases.
03 Use Envoy Proxy to control and gradually shift customer traffic.
04 Automatically detect deployment problems and roll back to the stable version.
05 Monitor deployment progress, application health, and transaction errors.

Application Workflow

01

Stage 1 – Customer Login

Process

The customer logs into the e-commerce application.

Tools
Keycloak PostgreSQL
Implementation

The customer enters their credentials. The application authenticates the customer and provides access to their account.

02

Stage 2 – Product Browsing

Process

The customer searches and browses available products.

Tools
PostgreSQL
Implementation

The application retrieves product information such as name, price, description, and availability and displays it to the customer.

03

Stage 3 – Shopping Cart

Process

The customer selects products and adds them to the shopping cart.

Tools
PostgreSQL
Implementation

The application stores the selected products and calculates the cart total.

04

Stage 4 – Order Placement

Process

The customer confirms the products and places an order.

Tools
PostgreSQL
Implementation

The application creates the order, records the customer and product details, and updates the order status.

05

Stage 5 – Payment

Process

The customer makes payment for the order.

Tools
Payment Service Payment Gateway PostgreSQL
Implementation

The application sends the payment request to the payment gateway. After successful payment, the order status is updated.

06

Stage 6 – Order Tracking

Process

The customer checks the status of their order.

Tools
PostgreSQL
Implementation

The application displays the current order status such as Confirmed, Processing, Shipped, or Delivered.

Cloud Infrastructure and Tools

Continuous Integration Tool GitHub Actions

Automates the application build, testing, and packaging process whenever new code is pushed or merged.

Release Orchestration Tool Spinnaker

Manages the application release process, including blue-green deployments, canary deployments, traffic progression, and automatic rollback when problems are detected.

Traffic Management Tool Envoy Proxy

Controls customer traffic and moves users between the old and new application versions during deployment.

Containerization Tool Docker

Packages the e-commerce application and its dependencies into containers so the application runs consistently in different environments.

Target Compute Infrastructure Cloud EC2 Instances

Provides the virtual servers used to run the e-commerce application, Spinnaker, and Envoy Proxy.

Server Operating System Ubuntu Server 24.04 LTS

Provides the stable Linux operating system for the EC2 servers.

Cloud Networking Infrastructure Cloud VPC

Creates the secure cloud network and separates public traffic from private application environments.

Security Controls & Firewalls Cloud Security Groups + Network ACLs

Control network access and protect the application servers from unauthorized traffic.

Persistent Storage Cloud EBS

Provides storage for the operating system, application files, deployment data, and logs.

Container/Image Storage Cloud ECR

Stores the Docker container images created by the deployment pipeline so they can be used during application releases.

Implementation Process

01
Step 1 – Audit Software and Traffic
  • Review the e-commerce application, payment routes, and user-session dependencies.
  • Define how customer traffic will move between the old and new versions.
  • Configure the deployment workflow in GitHub Actions.
  • Define the required routing and deployment settings.
02
Step 2 – Create the Two Application Environments
  • Create the secure Cloud VPC network.
  • Create Cloud EC2 servers using Ubuntu Server 24.04 LTS.
  • Create two environments: Blue → Current stable application; Green → New application version.
  • Attach Cloud EBS storage to the servers.
  • Configure Security Groups to protect the environments.
03
Step 3 – Build and Package the Application
  • Create Dockerfiles for the e-commerce application.
  • Use Docker to create application containers.
  • Configure GitHub Actions to automatically build and test the application.
  • Store successful container images in an artifact/container registry.
04
Step 4 – Configure Release and Traffic Management
  • Install and configure Spinnaker.
  • Deploy Envoy Proxy at the application entry point.
  • Connect Spinnaker with the application deployment process.
  • Configure Envoy to control traffic between Blue and Green environments.
  • Verify that traffic can be moved between the two environments.
05
Step 5 – Test Monitoring and Automatic Rollback
  • Monitor Spinnaker and Envoy deployment metrics.
  • Deploy a test version with an intentional error.
  • Send a small percentage of traffic to the new version.
  • If errors increase, Spinnaker automatically tells Envoy to send traffic back to Blue.
  • Test a successful release by gradually moving traffic from Blue to Green.
  • Finally, update the DNS configuration to point the domain to the Envoy gateway.

Proposed Solution

The solution combines GitHub Actions, Spinnaker, Envoy Proxy, and Docker to create an automated zero-downtime deployment system. The e-commerce application runs in two parallel environments on Cloud EC2. GitHub Actions builds and tests the application, Docker packages it, Spinnaker manages the release, and Envoy Proxy controls customer traffic. The new version is first tested with a small percentage of users. If it works correctly, traffic is gradually increased until all users are moved to the new version. If a problem occurs, traffic is automatically returned to the stable version.

Benefits

Zero-Downtime Updates: Customers can continue using the website during releases.
Automatic Rollback: Failed releases can automatically return to the stable version.
Safe Canary Releases: New versions can initially be tested with a small percentage of users.
Automated Deployment: GitHub Actions reduces manual deployment work.
Reduced Release Risk: Problems are detected before the new version reaches all customers.

Challenges

Database Schema Synchronization: The old and new application versions must work correctly with the database during the transition.
Canary Monitoring: Spinnaker must correctly identify real application problems without reacting to normal temporary network issues.
Higher Infrastructure Cost: Running Blue and Green environments at the same time requires additional Cloud compute resources.
← Back to Project Titles