Bùi Kiên CườngSolution Architect @ FSoft

A Case study of migrating an Oracle Application from on-premise to AWS

August 25 2016

1. Business Requirements2. Existing Architecture3. First Solution4. Our Solution5. Cost Saving6. Q&A

Meetup Agenda

General Introduction

• This is the core database and application for our customer business data. It is critical to both operational people and business analytical researchers. The system is the source for operational reports and analytical reports.

Hardware & Software

• 2 VMs: 32 cores, 100GB RAM• OS: Redhat• Storage: 2+ TB on disk array, 3000 IOPS, 50

MB/s.

Network/Security

• Network bandwidth: 5 Gbps• Global company: VPN Site to Site

DR & HA

• RTO: 24 hours. Aim for 2 hours.• RPO: 4 hours. Aim for 15 mins for future system.• HA: 99.5% ~ 5 nights down time per year.• Backup Retention:

– 3 days for 4 hours snapshots.– 60 days for daily backups.

Current Architecture

Challenges

• RTO of 2 hours, RPO of 15 mins.• No disk array on AWS Have to deal with bit rot,

disk failures.• Data growth 20% per year.• Choose Oracle RDS or Oracle on EC2?• Choose instance type that optimized for EBS.

First solution

• What are the problems?

Our Solution

• How is this solution better?

Cost Saving

• Instance type for instances: r3.4xlarge– 10 Gbps– 18000 IOPS for free

• Our solution: save 70% of AWS infrastructure cost.

Thank You

Meetup: www.meetup.com/aws-vn

FB: www.facebook.com/groups/amazonwebservicevietnam

Join Slack: https://aws-vn.herokuapp.com/