How Rooter Transitioned to MongoDB Atlas for Enhanced Gaming Performance and Scalability

Overview

Rooter, India's leading game streaming and esports platform, faced scalability issues with their existing MySQL database. Aiming for improved performance and flexibility, they partnered with Mydbops to migrate to MongoDB Atlas. Despite challenges with data transformation and schema adjustments, Mydbops' meticulous planning and execution ensured a smooth transition, allowing Rooter to efficiently manage burgeoning data needs and deliver an enhanced gaming experience.
10ms
Game Latency
Faster game-state retrieval and updates for players.
Horizontal
Scalability
Now supports a growing number of game players automatically.
Zero
Data Loss
Real-time data sync kept player records consistent during the move.
Global
Distribution
Game data is now placed closer to players to cut down delays.
MongoDB
Consulting Services

About

Rooter is a large-scale sports entertainment and gaming platform in India, built around live streaming, creator-led sports content, and interactive fan engagement. It has reached a wide audience across the country and operates at the intersection of sports media, gaming, and community, making it a strong example of a digital platform with meaningful user scale.
★★★★★
As India's leading game streaming platform with 75M+ installs, we handle massive traffic spikes during tournaments. Mydbops has been crucial in managing our database performance and costs for 4+ years. Their proactive monitoring, query optimization, and 24/7 support have helped us achieve seamless scaling. They deliver excellent technical expertise while keeping costs reasonable.
Rishabh Jain
Engineering Manager, Rooter
Deployment Type
Database Stack
Outcome
Cloud-Based Deployment
Migration from MySQL to MongoDB Atlas
Drop Latency to 10ms with improved ability to scale
Deployment Type
Cloud-Based Deployment
Database Stack
Migration from MySQL to MongoDB Atlas
Outcome
Drop Latency to 10ms with improved ability to scale

Business Challenges

Overview
Moving from a traditional database to a new system created several business challenges, primarily centered around keeping the games online and protecting player data during the transition.

Handling Growing Player Data: The old MySQL setup struggled to keep up with the increasing number of active players, which threatened the user experience.

Keeping Games Online During the Move: Rooter had to move millions of records without losing player data or causing long service interruptions. Real-time data sync was required to keep everything accurate.

Adapting to Game Changes: The strict structure of the old database made it difficult and slow for the developers to add new game features or adapt to changing requirements.

Data Consistency: Changing how player data was stored from traditional tables into a new format had to be done carefully to ensure no player accounts or game states were corrupted.

Goals
The key objectives the client was aiming to achieve:

Achieve database scalability and flexibility.


Improve the gaming user experience through better performance.


Simplify how data is managed and organized.


Keep service interruptions to a minimum during the database move.


Maintain complete data security and integrity.

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

Mydbops managed the transition by focusing on keeping the games running smoothly and securing player information:
Planning for Growth:

Reviewed the old database and designed a new structure that fits how game state data and player interactions actually work.

Safe Data Migration:


Created specific scripts to move player data safely. They adjusted the application code so the games could connect correctly to the new database without issues.

Performance Tuning:


Set up indexing and tuned the new database to make the game run as fast as possible.

Securing Player Data:


Set up strict security rules, including IP restrictions and encryption, to keep sensitive player information safe and meet industry standards.

Pre-Launch Testing:


Tested the new setup extensively to make sure the data was accurate and the game applications worked correctly before making the final switch.

Zero-Downtime Migration Process

1

Planning

Schema de-normalization and flexible data modeling for high concurrency.

2

Data Sync

ETL scripts created to safely transform tables to BSON format in real-time.

3

Security & Tuning

VPC Peering, IP Whitelisting, and deep index optimization executed.

4

Testing & Launch

Rigorous data integrity checks before switching over live gaming traffic.

Infrastructure Shift

Previous Setup (MySQL)

Scalability Limited Vertical Scaling
Response Time 200ms Latency
Data Location Centralized
Feature Adaptation Rigid & Hard to change
NEW ARCHITECTURE

MongoDB Atlas

Scalability Horizontal Scalability (Sharding)
Response Time 10ms Latency
Data Location Global Distribution Clusters
Feature Adaptation Flexible Schema for rapid updates

Results and Impact

Key Outcomes
Faster Gaming Experience

By changing how game-states are retrieved and updated, latency dropped from 200ms to just 10ms. This made the games much more responsive for the end user.

Dramatic Latency Reduction

Game-state retrieval response time before and after migration.

200ms 150ms 100ms 50ms 0ms
200
10
MySQL
(Before)
MongoDB
(After)

Ready for More Players

The new setup allows Rooter to scale horizontally. As the number of players grows, the database easily supports the extra load without slowing down the game.

Faster Game Updates

Because the new database structure is flexible, Rooter developers can easily add new game features and adapt to player requirements without rewriting the entire database structure.

Global Reach for Players

Using global clusters, Rooter can now store game data geographically closer to where the players are actually located, which further cuts down on game delays.

Easier Maintenance

Automated backups and monitoring mean the Rooter team spends less time fixing database issues and more time improving their games. Mydbops Managed Services continues to provide system inputs to keep things running well.

Business Impact Area
Before Migration
After MongoDB Atlas
Peak Traffic Handling
Slower game response
Auto-scales automatically
New Feature Rollouts
Delayed by rigid DB schema
Rapid deployment (Schema-less)
Global Player Experience
High latency across borders
Data localized via Global Clusters
Database Maintenance
High manual intervention
Automated backups & monitoring

Managing India’s largest game streaming platform is a constant race against real-time demands . With over 85 million registered users and massive traffic surges during live esports tournaments, Rooter’s engineering team faced a growing challenge: their legacy MySQL database was struggling to keep up. Every bottleneck meant a risk to player engagement, and rigid schemas delayed new feature releases.

The decision to transition to MongoDB Atlas was a strategic turning point. It wasn't just about changing a database; it was about building an infrastructure that could breathe with the platform. While remapping relational tables to a flexible document structure presented early challenges, careful step-by-step planning and real-time data synchronization allowed the team to complete the transition without interrupting active users.

Today, the technical upgrade translates directly into business value. With database latency dropped from 200ms to just 10ms, Rooter’s players experience immediate, lag-free game-state updates. The platform now automatically scales to absorb sudden tournament traffic spikes, and developers deploy new features without database bottlenecks. By solving their database scaling challenges, Rooter has built a solid foundation to support their next phase of growth.

Planning a database migration?

We help engineering teams set up, move, and manage MongoDB and MySQL databases so they stay online during traffic surges. Let's chat about your database scaling challenges.

Consult with a Certified Migration Expert

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