This document discusses different data storage solutions including static storage like Amazon S3, file systems using Amazon EBS, sync volumes with AWS Storage Gateway, relational databases with Amazon RDS, and NoSQL databases like Amazon DynamoDB. It provides an overview of each solution and when they would be applicable, focusing on characteristics like scalability, durability, ease of administration and cost. The overall message is that the right choice depends on your specific needs and priorities around performance, manageability and budget.

1. CHOOSING THE RIGHT
DATA STORAGE
SOLUTION
Carlos Conde │Solutions Architect

2. 1. STATIC STORAGE
2. FILESYSTEMS
3. SYNC VOLUMES
4. RELATIONAL DATABASES
5. NoSQL DATABASES

3. # 1
STATIC STORAGE
●○○○○

4. We are constantly producing more data

5. AMAZON S3
SIMPLE STORAGE SERVICE

10. 99.999999999%
DURABILITY

11. ORACLE
SECURE BACKUP MODULE
ORACLE RMAN  AMAZON S3

13. USE AMAZON S3
WHEN YOU NEED:
 Unlimited storage capacity
 High durability
 Storage for backups
 Web access to data
+ Amazon CloudFront

14. # 2
FILESYSTEMS
●●○○○

15. EPHEMERAL STORAGE

16. AMAZON EBS
ELASTIC BLOCK STORAGE

17. 10GB  TB

21. EBS
SNAPSHOTS

23. USE AMAZON EBS
WHEN YOU NEED:
 Filesystem for an instance
NTFS, ExtFS, RAID, LVM…
 Long-term persistent storage
 Data changes frequently
 Access to raw, unformatted block-
level storage

24. # 3
SYNC VOLUMES
●●●○○

25. BACKUP
MANAGEMENT

26. AWS STORAGE
GATEWAY

29. USE AWS STORAGE
GATEWAY
WHEN YOU NEED:
 Backup your data
 Synchronize data for disaster
recovery
 Export data for migration

30. # 4
RELATIONAL
DATABASES
●●●●○

32. WHAT ABOUT…
 BACKUPS?
 SCALING?
 UPDATES?
 MONITORING?
 REPLICATION?

33. AMAZON RDS
RELATIONAL DATABASE SERVICE

39. BACKUPS
&
SNAPSHOTS

43. READ REPLICAS
READ-ONLY ASYNCHRONOUS REPLICA

47. RDS MULTI-AZ
STAND-BY SYNCHRONOUS REPLICA

50. USE AMAZON RDS
WHEN YOU NEED:
 Relational database engine
(MySQL, SQLServer, Oracle)
 Peace of mind about your data
 More time!

51. # 5
NoSQL DATABASES
●●●●●

53. The scalability challenge
Requirement: predictable,
consistent performance
Performance
Hardware provisioning
Data sharding
Data caching
Cluster management
Reality: performance
degrades with scale Fault management
Scalability

54. AMAZON
DYNAMODB
HIGH-PERFORMANCE, FULLY MANAGED
NoSQL DATABASE SERVICE

55. LOW LATENCY
AVERAGE READS < 5MS,
WRITES < 10MS

56. SEAMLESS
SCALABILITY
NO TABLE SIZE OR THROUGHPUT LIMITS
LIVE REPARTITIONING

57. PREDICTABLE
PERFORMANCE
PROVISIONED THROUGHPUT MODEL

58. DURABLE
& AVAILABLE
CONSISTEN, DISK-ONLY WRITES (SSD)

59. ZERO
ADMINISTRATION

62. USE AMAZON DYNAMODB
WHEN YOU NEED:
 Low latency on R/W operations
+ Scalability
+ Data durability
 Predictable performance

63. 1. STATIC STORAGE
2. FILESYSTEMS
3. SYNC VOLUMES
4. RELATIONAL DATABASES
5. NoSQL DATABASES

65. IT’S ALL ABOUT
CHOICE
PERFORMANCE-ORIENTED
COST-ORIENTED