E-commerce company in Bangladesh
A leading online store in Bangladesh struggled with downtime and slow recovery at festival peaks. We moved it from its own servers to AWS in three phases.
The facts
The result
1,000 to 6,000+ ordersOrders the platform can handle in a peak, before the move and after it
Order capacity
Three phases, one after another
The platform moved in stages, so the customer could see each step.
- Step 1: AssessA rapid discovery and a Well-Architected review, with a report of high-risk and medium-risk issues.
- Step 2: MobilizeA business case, an operating model, and a migration strategy for each application.
- Step 3: MigrateSmall parts moved first, then the rest, with the customer able to see each step.
The challenge
- Always on, most of all at Eid, Pohela Boishakh and Durga Puja.
- Downtime and slow recovery from failures on its own servers.
- Falling customer satisfaction, and a slowed supply pipeline.
What we did
- Ran a rapid discovery and a Well-Architected review, which listed high-risk and medium-risk issues.
- Briefed stakeholders and built a business case with a total cost of ownership view.
- Ranked the applications and chose a migration strategy for each.
- Moved the applications in stages, so the customer saw each step.
- Modernized the applications as they moved, to keep cost under control.
- Added a synchronized queue for orders, inventory and payments.
How it was built
- Compute and network
- Amazon EC2
- Application Load Balancer
- NAT gateway
- Elastic IP
- Amazon Route 53
- Data and cache
- Amazon RDS for MySQL
- Amazon ElastiCache for Redis
- Amazon DynamoDB, on demand
- Amazon S3
- Amazon EBS
- Events and mail
- Synchronized order queue
- AWS Lambda
- Amazon SES
- Audit and monitoring
- AWS CloudTrail
- Amazon CloudWatch
What came of it
- Order capacityMore than 6,000 orders, up from a previous limit of 1,000.
- GrowthA larger user base, with better responsiveness and resilience.
- Cost and securityCloud adoption made costs easier to manage, and security improved.