Skip to content
Md. Saydur Rahman (Saydur), DevOps Engineer

Md. Saydur Rahman

DevOps & Infra Professional

Availability

Available for projects

Replies within 24h

Back to Case Studies

Fintech · national payment gateway

ekPay.

ekPay logo

DevOps Engineer · CI/CD & Releases

ekpay.gov.bd (opens in a new tab)

ekPay is Bangladesh's national payment gateway. People use it to pay government and utility bills online. It handles live payments, so every release must keep transactions flowing.

It is one of the a2i platforms, along with Nothi and NPF, that together serve more than 5 million users with 99.9% uptime.

Tech Stack

DockerJenkinsHarborConsulNginxKubernetes (PoC)

My Role

My work on ekPay is about deployment. I build and look after the CI/CD pipelines, run releases and keep the gateway online during every deploy.

I also built a Kubernetes proof of concept to test moving ekPay's containers onto Kubernetes.

Architecture

Jenkins builds each ekPay service into a Docker image and pushes it to a private Harbor registry. Services run on Docker hosts and register themselves in Consul. Nginx reads the list of healthy services from Consul and only sends payment traffic to them. A separate Kubernetes proof of concept ran the same images with rolling updates and readiness checks.

Challenges & Solutions

Payments keep flowing around the clock. Releases needed to become automatic and repeatable while live traffic continued, with a fast and safe way back to the previous version.

  1. CI/CD pipelines

    Jenkins builds each service into a Docker image, gives it a version number and pushes it to our private Harbor registry. Every environment deploys the exact same image.

  2. Release process

    The same image moves from one environment to the next. Each version is saved in Harbor, so a rollback just means deploying the previous version.

  3. Always-online deploys

    Services register in Consul, and Nginx only sends traffic to healthy ones. During a release, new instances start and pass their health checks before the old ones are removed. Users only ever reach containers that are ready.

  4. Kubernetes trial

    A proof of concept ran the same images on Kubernetes, with rolling updates, readiness checks and self-healing, as a next step after Docker hosts with Consul and Nginx.

Results

  • The payment gateway stays online through every release.
  • Every deploy is a saved image in Harbor, so rollback is fast and safe.
  • Part of the a2i platforms serving 5M+ users with 99.9% uptime.