Developers and DBAs from a traditional relational background are spoilt for choice when looking to integrate caching and NoSQL into an application architecture to solve scaling problems and reduce costs. Even when using relational databases there are 3 managed database services on AWS for the MySQL engine alone. Trying to evaluate all the options often creates analysis paralysis, resulting in a reluctance to try something new or different. This session will guide you through a series of use cases that use different databases to solve business problems that customers face today.
7. Power, HVAC, net
Rack & stack
Server maintenance
OS patches
DB s/w patches
Database backups
Scaling
High availability
DB s/w installs
OS installation
Query Construction
Query Optimisation
Schema Design
Traditional
DC
Why Managed Databases?
8. Power, HVAC, net
Rack & stack
Server maintenance
OS patches
DB s/w patches
Database backups
Scaling
High availability
DB s/w installs
OS installation
Query Construction
Query Optimisation
Schema Design
Power, HVAC, net
Rack & stack
Server maintenance
OS patches
DB s/w patches
Database backups
Scaling
High availability
DB s/w installs
OS installation
Query Construction
Query Optimisation
Schema Design
DB
on EC2
Why Managed Databases?
Traditional
DC
9. Power, HVAC, net
Rack & stack
Server maintenance
OS patches
DB s/w patches
Database backups
Scaling
High availability
DB s/w installs
OS installation
Query Construction
Query Optimisation
Schema Design
Power, HVAC, net
Rack & stack
Server maintenance
OS patches
DB s/w patches
Database backups
Scaling
High availability
DB s/w installs
OS installation
Query Construction
Query Optimisation
Schema Design
Power, HVAC, net
Rack & stack
Server maintenance
OS patches
DB s/w patches
Database backups
Scaling
High availability
DB s/w installs
OS installation
Query Construction
Query Optimisation
Schema Design
Managed
Database
Why Managed Databases?
DB
on EC2
Traditional
DC
26. “In a physical data center, I would need at least 3
administrators to maintain the infrastructure and ensure
similar levels of availability”
- Richard Glew, CTO
30. ID Name
1 John Smith
2 Jane Jones
3 Peter Black
4 Pat Partridge
5 Sarah Cyan
6 Brian Snail
1 John Smith
4 Pat Partridge
2 Jane Jones
5 Sarah Cyan
3 Peter Black
6 Brian Snail
Massively Parallel
JDBC/ODBC
31. • Column storage
• Data compression
• Zone maps
ID Age State Amount
123 20 QLD 500
345 25 WA 250
678 40 NSW 125
957 37 WA 375
Reduces I/O
Row storage
Have to read the
entire row
32. Column storage
Only read the
data you need
• Column storage
• Data compression
• Zone maps
Reduces I/O
ID Age State Amount
123 20 QLD 500
345 25 WA 250
678 40 NSW 125
957 37 WA 375
35. “When our analysts first started to do queries on
Amazon Redshift they thought it was broken
because it was working so fast”
- FT CTO John O’Donovan
36. “We intend to grow 100x in terms of
data size in the next few years”
- Kaushik Paranjape, CTO
39. ID Age State
123 20 CA
345 25 WA
678 40 FL
Relational Table
ID Attributes
123 Age:20, State:CA
345 Age:25, Country: Australia, Gender: F, Smoker: No
678 Age:40
Non-Relational Table
Relational vs non-relational
52. “The latency of a cab call must be low, and remain low even
in times of peak traffic of hundreds of thousands of cab
requests per minute.“
Ryan Ooi
Sr. Devops Engineer, Grab