Executive Summary:
Truemeds, one of India’s leading online pharmacies, needed infrastructure that could keep up with rapid growth, protect its fulfilment operations and let its team release features faster.
Rapyder containerised all 33 of Truemeds’ microservices on Amazon EKS, isolated the Warehouse application in its own cluster, automated deployments with Jenkins and put governance and monitoring in place across dedicated Dev and Prod accounts.
The result: 99.9% platform availability, deployments cut from around 2 hours to under 15 minutes, 4× more frequent releases and roughly 30% lower infrastructure costs.
About Customer:
Truemeds is an online pharmacy providing genuine, affordable medicines and healthcare products to customers across India. Founded in 2015, it has grown into one of the country’s leading online pharmacies, offering prescription and over-the-counter medicines, vitamins and supplements, with delivery options including same-day delivery in select cities. Truemeds is a registered member of the Indian Pharmaceutical Association.
Industry:
Industries, Healthcare / HealthTech
Offering:
Offerings, Modernization
Business Challenges:
- Keeping the pharmacy available as demand grew – Customers ordering prescription medicines for same-day delivery need a reliable app. The existing setup lacked automatic scaling and high availability, while peak traffic reached 3× normal volumes, putting orders and customer experience at risk.
- A complex, 33-service estate with no clear cloud migration path – Two applications spanning 33 services needed careful dependency mapping to avoid disruption during migration. Building, configuring and managing each service separately consumed engineering time and made scaling difficult.
- Fulfilment operations exposed to customer-side risk – All 12 warehouse services shared infrastructure risk with the customer app. A traffic surge or fault could disrupt picking and dispatch, jeopardising delivery commitments.
- Slow, manual releases holding back innovation – Manual builds and deployments across 33 services were slow and error-prone. Each deployment took around 2 hours, limiting release frequency and slowing Truemeds’ response to market demand.
- Limited governance, visibility and cost control – Dev and Prod needed dedicated accounts, while teams lacked a unified view of infrastructure and application health. Late issue detection and resource sizing without usage data led to avoidable costs.
Solution Implemented:
- Highly available, scalable hosting on Amazon EKS – All services are hosted on Amazon EKS in the AWS Mumbai region. Traffic is routed through Kubernetes ingress and the Kong API gateway, and workloads scale with demand to deliver high availability.
- Assessment-led containerisation of all 33 services – Guided by the assessment blueprint, Rapyder containerised and deployed all 33 microservices (21 customer-facing, 12 warehouse) onto EKS in a standardised way.
- A dedicated Warehouse Application Cluster – The Warehouse application runs in its own cluster with a dedicated namespace, fully separate from the customer-facing application.
- Automated CI/CD with Jenkins – Jenkins pipelines handle continuous build and deployment of microservices onto the EKS clusters, giving the team a repeatable, automated release process.
- Multi-account governance, monitoring and right-sizing – Dev and Prod run in dedicated accounts under AWS Organizations. Amazon CloudWatch, Prometheus and Grafana provide visibility into infrastructure and application health, and EKS resources are allocated precisely to match workload needs.
Technology Stack:
- Amazon EKS
- Amazon CloudWatch
- Jenkins
- Kong
- Prometheus
- Grafana
Business Benefits:
- Enhanced performance and scalability – Establishing an EKS cluster for Prod and Staging improved application performance and scalability, letting the business handle increased user traffic with a seamless experience.
- Efficient deployment process – Jenkins pipelines for CI/CD streamlined deployment, enabling quicker releases of new features and faster response to market demands.
- Cost savings through resource optimisation – Precise resource allocation on EKS translated into potential cost savings by avoiding unnecessary infrastructure spend.
Ready to Scale Your Platform Like Truemeds? Whether you are modernising a microservices application, moving to containers or held back by slow releases, Rapyder’s AWS experts can help you build infras
Key Takeaways:
- Assess before you migrate – mapping how services interact up front made a 33-service move predictable.
- Isolate critical operations – a dedicated warehouse cluster keeps fulfilment running even when customer traffic spikes.
- Automate releases early – CI/CD turns deployment from a bottleneck into a competitive advantage.
- Build in visibility and governance from day one – monitoring and separate accounts keep a growing platform secure and cost-efficient.
Frequently Asked Questions
Truemeds had outgrown its infrastructure and needed to move a live, 33-service pharmacy platform to AWS without putting customer orders at risk. It needed a partner with hands-on expertise in AWS, Kubernetes and DevOps who could plan the move carefully, separate its warehouse operations and automate releases. Rapyder brought that combination of cloud and DevOps experience.
Rapyder assessed both applications, designed the target setup on AWS and containerised all 33 microservices onto Amazon EKS in the AWS Mumbai region. It also gave the Warehouse application its own cluster, built Jenkins CI/CD pipelines, set up separate Dev and Prod accounts under AWS Organizations, and put monitoring in place with Amazon CloudWatch, Prometheus and Grafana.
Rapyder took an assessment-first approach. Before moving anything, the team mapped how every service worked and depended on the others, so design decisions were based on Truemeds’ real workloads rather than a generic template. This reduced migration risk and kept the project predictable.
Rapyder moved the 12 Warehouse services into a dedicated cluster and namespace, fully separate from the customer-facing app. Traffic spikes or issues on the customer side can no longer slow down inventory and dispatch, so Truemeds can keep its delivery promises.
Rapyder replaced manual release steps with automated Jenkins pipelines that build and deploy each microservice onto EKS. Deployments dropped from around 2 hours to under 15 minutes, and Truemeds now releases 4× more often.
Rapyder sized EKS resources to match actual workload needs and set up dashboards that show infrastructure and application health in real time, so the team spots issues early and avoids paying for idle capacity. Infrastructure costs are about 30% lower, and issues are detected 50% faster.
