Rapyder Migrates a Ride-Sharing Startup from GCP to AWS

Customer success story · Migration
Rapyder Migrates a Ride-Sharing Startup from GCP to AWS

Rapyder migrated a Ride-sharing startup from GCP to AWS Cloud to cater to their mobile app APIs with backend Database as MySQL.

ecommerce cloud solutions
PublishedNovember 25, 2019IndustryIT- ITeSServiceMigration
Case StudyMigration
01

The Challenge

The Customer was running multiple workloads on the Google Cloud Platform and had planned to migrate their entire B2C application from GCP to AWS. These were Java-based applications to cater to their customer-facing mobile app APIs with Backend Database as MySQL.

This migration was expected to be done with very minimal downtime of maximum 30 minutes.

02

The Solution

Consultants at Rapyder had detailed discussions with the Client to understand their requirements and studied the working of their application portfolio to provide an optimum solution for the migration. To address the objectives defined in the statement of work, our Solution Architects stitched the solution around AWS services.

The following solution was implemented:

Step 01

AWS Mumbai region was considered for the hosting of applications.

Step 02

All the servers behind the application load balancers were provisioned in private subnets in different AZ, which was behind the load balancer.

Step 03

Load balancer would offload the SSL certificate and send traffic to the appropriate instance.

Step 04

Public-facing servers were launched in a public subnet based on the requirement.

Step 05

OpenVPN server was provisioned to connect directly to the instances in private servers from local.

Step 06

RDS MySQL with Read replica was configured for Database.

Step 07

AWS ACM used for SSL certificates to be applied on the load balancer.

Step 08

ElasticSearch was provisioned to be used as managed service and was replicated to AWS by backup and restore.

Step 09

RabbitMQ and ActiveMQ were configured on EC2.

Step 10

NAT Gateway was used for all outgoing internet connections from private servers.

Step 11

AWS CloudTrail is enabled to monitor activity on the AWS account.

Step 12

AWS CloudWatch setup is done by monitoring the servers.

Step 13

Route53 will be used as DNS Service for weighted routing between GCP and AWS before routing 100% of traffic to AWS.

Step 14

Database Migration was used for migration as the Customer had a very slim window for the cut-over to production.

03

The Outcome

  • Highly available and very scalable architecture has been provisioned at all layers.
  • The Client is expecting huge growth in its customer base year-on-year, and with the infrastructure provisioned by Rapdyer, they are now well-prepared to meet the challenges of the near future.

Case Studies

Share

Search Case Studies

Recent Case Studies

Categories

Tags

Subscribe to the
latest insights

Subscribe to the latest insights

Related Case Studies

How Rapyder delivers 24/7 AWS managed services for VouchaGram (GyFTR), migrating to Aurora Serverless and achieving 100% uptime during campaign spikes.
Rapyder migrated 1.5+ petabytes of Qualtrics Elasticsearch, Kafka and PostgreSQL from IBM bare metal to AWS with zero data loss and 99.99% uptime.
How Rapyder containerised Truemeds’ 33-service healthcare platform on Amazon EKS with Jenkins CI/CD and Prometheus and Grafana monitoring.

Get in Touch!

Are you prepared to excel in the digital transformation of healthcare with Rapyder? Let’s connect and embark on this journey together.

Right arrow icon

Let’s Tackle Your Cloud Challenges Together

I accept  T&C and  Privacy  
Consult Now WhatsApp