Pleased with the results of its Amazon Redshift adoption, the company decided to move its entire service to AWS. “We want vendors to manage as much of the technology as possible, so we can focus on the customers and algorithms that are the main drivers of value in our matchmaking business,” says Poddar. The company began the migration to AWS in January 2016 and completed it by the end of March 2016.

The environment takes advantage of Amazon Elastic Compute Cloud (Amazon EC2) for processing across the platform, Amazon Simple Storage Service (Amazon S3) for object storage, and Amazon Simple Notification Service (Amazon SNS) for coordination among individual services. Amazon ElastiCache handles distributed in-memory data storage.

For databases, Shaadi.com uses both Amazon Relational Database Service (Amazon RDS) and Amazon Aurora depending on performance needs. Shaadi.com used the fully managed AWS Database Migration Service to keep source databases operational during the migration. “AWS Database Migration Service enabled us to keep downtime short as we moved from our private cloud to Amazon RDS and Amazon Aurora,” says Poddar.

The company migrated its systems without significant code changes, yet could adopt best-of-breed AWS services for each use case. It switched from a single dedicated load balancer to several instances of Elastic Load Balancing to meet individual service requirements. It simplified database management with Amazon DynamoDB. And, it has started to use the Amazon Elasticsearch Service for rapid searching of big data, which provides 30 percent faster results than the company’s previous solution.