The bill, before and after
| Before | After | Change | |
|---|---|---|---|
| Cloud infrastructure (monthly) | US$8,350 on AWS | US$5,511 on Azure | 34% lower |
| Database (monthly) | US$3,700 for MongoDB | US$2,165 on Azure DocumentDB | 41% lower |
| Total (monthly) | US$12,050 | US$7,676 | 36% lower |
| Saving per year | About US$52,488 | ||
Azure infrastructure is shown at 34% below the previous AWS bill, rounded to the nearest dollar.
The client
Gamerji is an Indian gaming platform. Its players expect the platform to be there whenever they want to play, so any move had to keep disruption to a minimum.
The challenge
The aim was simple: a lower monthly cost, without making the platform slower or less reliable for players.
Gamerji ran on AWS, with its MongoDB databases on a separate MongoDB bill. Together they came to US$12,050 a month. The aim was simple: a lower monthly cost, without making the platform slower or less reliable for players.
What we did
- 01Assessment
We mapped every part of Gamerji’s AWS setup and the MongoDB databases, and how much each one really used.
- 02Plan and cost
We matched each AWS service to its Azure equivalent, sized for actual use rather than copied one for one, and priced the result before anything moved.
- 03Database move
We moved the MongoDB data to Azure DocumentDB, Microsoft’s managed MongoDB-compatible database, so the application kept talking to a MongoDB-style database.
- 04Build and test
We built the Azure environment alongside AWS and tested it before switching.
- 05Switch-over
The final move happened in one short planned window at a quiet time for players.
Built with
- Azure
- Azure DocumentDB
The result
Cloud infrastructure cost 34% less each month: US$8,350 on AWS down to about US$5,511 on Azure.
The database cost 41% less: US$3,700 down to US$2,165 a month on Azure DocumentDB.
Overall, the monthly bill fell from US$12,050 to US$7,676, a saving of about US$4,374 a month, or about US$52,488 a year.
What other teams can take from this
- Price before you move Sizing for real usage, not copying the old setup, is where much of the saving comes from.
- Look at the database bill separately A managed, compatible database on the new cloud can cut a separate database bill sharply.
- Plan one clean switch-over Build alongside, test, then move in a short window at your quietest time.
Questions people ask
How long did Gamerji’s migration take?
Three weeks from start to finish, with one short planned switch-over window at a quiet time for players.
How much did Gamerji save?
Its monthly cloud bill fell from US$12,050 to US$7,676, about 36% lower, or roughly US$52,488 a year.
What is Azure DocumentDB?
Microsoft’s managed database on Azure that is compatible with MongoDB, so applications built for MongoDB can use it.
Is your cloud bill higher than it should be?
Book a free migration assessment. We price your setup on the cloud that fits, before anything moves.
