Nykaa’s 70% AWS Cost Cut & 3X Performance Boost

Overview

Nykaa hit slowness from poor query design blocking fast checkouts during flash sales. High CPU spikes slowed master/replicas in peak evening hours. DB locking caused abandoned carts costing revenue. Over-provisioned RDS wasted budget without performance gains. Mydbops partnership eliminated bottlenecks and cut infrastructure spend. Seamless festive sales processing restored instantly.
70
%
Cost Savings
Massive savings post RDS optimization
3
x
Query Performance
Significantly faster response and data processing
3
x
CPU Usage
Heavy load dropped after query and config tuning
2
x
Concurrency Handling
Handled peak load with no locking issues
MySQL
Managed Services

About

Nykaa-Mydbops
Nykaa serves 52M customers with 32M beauty buyers and 276 stores in 94 cities. Q3 FY26 revenue hit ₹2,873 crore (27% YoY growth), beauty GMV ₹3,390 crore (32% YoY). Processed strong festive sales with 84M+ visits in Pink Summer. Leads omnichannel beauty/fashion with 25-28% annual growth guidance.
★★★★★
Nykaa-Mydbops
Deployment Type
Database Stack
Outcome
Cloud-Based Deployment
Amazon RDS for MySQL
$370,220 Saved Annually
Deployment Type
Cloud-Based Deployment
Database Stack
Amazon RDS for MySQL
Outcome
$370,220 Saved Annually

Business Challenges

Overview
The client experienced major performance degradation and soaring infrastructure costs due to inefficient MySQL RDS configuration, query patterns, and scaling issues.

‼️ Database Slowness Due to Poor Query Design: Several unoptimized queries caused slow response times and blocked transactions, directly impacting user experience.

‼️ High CPU Usage on Master and Replicas: The master node and replicas frequently experienced CPU spikes, leading to latency in read/write operations.

‼️ DB Locking During High Concurrency: During flash sale events or peak evening hours, users faced slow page loads due to locking issues, resulting in abandoned carts and lost sales.

‼️ Over-Provisioned and Costly Infrastructure: The client was spending over $44,000 per month, including AWS Enterprise Support, without seeing corresponding performance benefits.

Goals
The key objectives the client was aiming to achieve:

Optimize Resource Usage: Scale down to appropriate instance sizes without impacting performance.    

→ Improve Query Response Time: Reduce latency and ensure quick database responses for both read and write operations.

→ Handle Traffic Spikes Gracefully: Eliminate DB locks and improve concurrency handling during high user traffic.    

→ Reduce AWS Expenditure Significantly: Cut unnecessary costs tied to oversized instances, high IOPS, and premium support.

Risks if Not Addressed
If left unresolved, these challenges posed serious risks

Risks & Impact if Not Addressed

Performance Issues

Without resolving replication lag and fragmented tables, query performance would continue to degrade, leading to a frustrating customer experience during peak hours.

Business Continuity Risks

Non-standardized backup policies increased the risk of data loss and prolonged outages, potentially disrupting thousands of orders in real-time.

Revenue Loss

Poor performance and downtime during peak times directly impacted Swiggy’s ability to fulfill customer demand, resulting in lost revenue and dissatisfied users.

Escalating Costs

Continued reliance on oversized, under-optimized infrastructure would lead to unnecessary monthly spend, straining the company’s profitability.

Developer Inefficiency

Lack of a stable and scalable database foundation meant developers spent significant time firefighting performance issues instead of innovating on features.

Performance Issues: Replication lag and fragmentation slow order searches and transactions.
Business Continuity Risks: Non-standardized backups mean longer recovery times and higher data-loss risk.
Revenue Loss: Slow page loads or timeouts during peak hours lead to failed checkouts.
Escalating Costs: Over provisioned, under-optimized servers strain profitability
Developer Inefficiency: Engineers spend more time firefighting than building new features
Goals
The key objectives the client was aiming to achieve:
→   
[Goal 1]
→   
[Goal 1]
→   
[Goal 1]

Solution Provided by Mydbops

Our team of MySQL consultants, with deep expertise in RDS and large-scale architectures, implemented a structured consulting process:

▸ RDS Instance Review & Slow Query Profiling

We began with a detailed review of their RDS setup — including instance types, configurations, storage, and slow queries — using both AWS tools and our internal profiling frameworks.


Right-Sizing of Instances

Our analysis revealed the client’s database instances were significantly over-provisioned. We strategically right-sized the master and replica servers to align their capacity and cost directly with their actual workload needs, delivering huge savings without affecting performance.

Nykaa: MySQL RDS Optimization Architecture

Query Optimization and Indexing

We profiled high-load queries and added missing secondary indexes. Bad queries were rewritten and query plans optimized, cutting CPU and I/O load drastically.


DB Parameter and Concurrency Tuning

RDS parameters (like max_connections, innodb_buffer_pool, query_cache_type, etc.) were tuned based on workload. This resolved locking issues and enabled smooth multi-user access.


IOPS Optimization Planning

We proposed and planned for the removal of over-provisioned 5000 PIOPS, which were not providing proportional performance benefits.


AWS Support Cost Elimination

Since Mydbops took over DB performance and reliability, the client was able to remove $15,000/month AWS Enterprise Support — a major cost saving.

Initial AWS Database Infrastructure Cost Summary
SI:NO Description Instance Type Storage Multi AZ PIOPS Cost ($)
1 Master × 1 db.r4.16xlarge 1000GB YES 5000 16,058.62
2 Slave × 3 db.r4.8xlarge 1000GB NO 5000 13,223.21
3 AWS Enterprise Support NIL NIL NIL NIL 15,000.00
TOTAL $44,281.83

All calculations were made using AWS cost calculator.

Optimized AWS Database Infrastructure Cost Summary
SI:NO Description Instance Type Storage Multi AZ PIOPS Cost ($)
1 Master × 1 db.r4.8xlarge 1000GB YES 5000 8,051.84
2 Slave × 3 db.r4.4xlarge 1000GB NO 5000 5,378.28
3 AWS Enterprise Support NIL NIL NIL NIL 0.00
TOTAL $13,430.12

Nykaa - AWS Cost Reduction Database Infrastructure Annual Cost Savings (ARR) $600K $450K $300K $150K $0 ANNUAL COST (USD) BEFORE $531,382 AFTER $161,162 Before Mydbops After Mydbops SAVED 69.7% $370,220

Results and Impact

Key Outcomes

✅  3x Boost in Query Performance

Optimized indexes and rewritten queries drastically reduced response time and improved application fluidity.


✅  $370,220 Saved Annually

Instance downsizing + support cancellation resulted in a >70% reduction in annual AWS costs.


✅  3x Drop in CPU Load on Master Node

Reduced CPU spikes led to a more stable production environment.


✅  2x Better Concurrency Handling

Users were able to browse and checkout during peak traffic with no locking issues.


✅  Improved Observability

Our team set up monitoring dashboards and health checks to ensure DB performance remains optimal long-term.

This case study showcases how Mydbops can transform a struggling MySQL infrastructure into a lean, high-performing system — delivering real value in cost, performance, and scalability. The client was able to shift from firefighting mode to focusing on business growth.

If your database performance is draining your cloud budget or impacting your users, it’s time to talk to Mydbops. Let’s help you turn your database into a growth asset.

Let’s Cut Your AWS Costs

Need Expert Database Solutions?

Talk to a Database Expert Today!

Database solutions are provided by mydbops expert team
Mydbops set up High Availability (HA) Solutions with InnoDB or Percona Clusters, ensuring continuous uptime and fault tolerance.
Thank You!
We’ve got your request, our expert team will be contacting you shortly.
Oops! Something went wrong while submitting the form.
Download Case Study