Databases Flashcards
What database services are available on AWS?
RDS (OLTP) DynamoDB (NoSQL) RedShift (OLAP) Elasticache (in memory caching) DMS
What is Multi-AZ RDS?
Multi-AZ allows to have an exact copy of your production database in another AZ. In the event of planned DB maintenance, BD instance failure, or an Availability Zone failure, Amazon RDS will automatically failover to the standby.
What is the use case for Multi-AZ RDS
Multi-AZ is for disaster recovery. It is not used for improving performance. For performance improvement, Read Replicas are needed.
Can Multi-AZ be used to performance improvement?
No. Multi-AZ is for disaster recovery. It is not used for improving performance. For performance improvement, Read Replicas are needed.
For which RDS databases “Read Replicas” is supported?
MySQL
MariaDB
PostgreSQL
Amazon Aurora
What is the use case for Read Replicas?
Read Replicas are used for scaling, not for disaster recovering.
How many Read Replicas can be added to a RDS BD?
Amazon RDS allow you to add up to 5 read replicas to each DB Instance.
Can Multi-AZ databases have Read Replicas?
Yes. You can create Read Replicas of Multi-AZ source databases.
How can you scale up in RDS?
It’s a manual process.
- Snapshot, Restore changing instance size.
- Read replica with bigger size.
What NoSQL data models support DynamoDB?
Document and key-value data models.
What kind of storage does DynamoDB uses?
Stored on SSD storage.
How is DynamoDB spread?
Spread across 3 geographically distinct data centers.
What Read Consistency models does DynamoDB supports?
Eventual Consistent Reads (default)
Strongly Consistent Reads.
What is “Eventual Consistent Reads”?
Consistency across all copies of data is usually reached within a second.
What is “Strongly Consistent Reads”?
A Strongly Consistent Read returns a result that reflects all writes that received a successful response prior to the read.
What AWS platform is most suitable for OLTP?
RDS/DynamoDB
Aurora Scaling
- 6 copies of data: 2 in each of a minimum of 3 AZs.
- Designed to handled transparently the loss of up to 2 copies of data without affecting write availability and 3 without affecting read availability.
- Self-healing (data blocks and disks continuously scanned)