22: Databases in AWS Flashcards

1
Q

Database Types: RDBMS

A

SQL / OLTP, Aurora - great for joins

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Database Types: NoSQL

A

no joins, no SQL - DynamoDB (~JSON), Elasticache (key / value pair), Neptune (graph), DocumentDB (MongoDB), Keyspaces (Apache Cassandra)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Database Types: Object Store

A

S3 (big objects), Glacier (backups / archives)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Database Types: Data Warehouse

A

SQL Analytics / BI: Redshift (OLAP), Athena, Elastic MapReduce (EMR)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Database Types: Search

A

OpenSearch (JSON) - free text, unstructured searches

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Database Types: Graphs

A

Neptune - displays relationships between data

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Database Types: Ledger

A

Amazon Quantum Ledger Database

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Database Types: Time Series

A

Amazon Timestream

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

RDS Summary: Engine Type

A

Managed PostgreSQL / MySQL / Oracle / SQL Server / MariaDB / Custom

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

RDS Summary: What to Provision

A

Instance size, EBS Volume Type, and size.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

RDS Summary: Capabilities

A

Autoscaling for storage, support for read replicas and Multi-AZ

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

RDS Summary: Security

A

Done through IAM, Security Groups, KMS, SSL in Transit

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

RDS Summary: Backup

A

Automated backup with point-in-time restore for 35 days, or Manual DB Snapshot for longer-term recovery

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

RDS Summary: Maintenance

A

Managed and Scheduled maintenance with downtime

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

RDS Summary: Authentication

A

Support for IAM authentication, integration with Secrets Manager

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

RDS Summary: Customize

A

RDS Custom for access to, and customize underlying instance (Oracle & SQL Server)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

RDS Summary: Use Case

A

Store relational datasets (RDBMS / OLTP), perform SQL queries and transactions

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Aurora Summary: API

A

Compatible API for PostreSQL / MySQL, separation of storage and compute

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

Aurora Summary: Storage

A

Stored in 6 replicas, across 3 AZ, highly available, self-healing, auto-scaling

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

Aurora Summary: Compute

A

Cluster of DB instance across multiple AZ, auto-scale of read replicas

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
21
Q

Aurora Summary: Cluster

A

Custom endpoints for writer and reader DB instances

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
22
Q

Aurora Summary: Security

A

Done through IAM, Security Groups, KMS, SSL in Transit

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
23
Q

Aurora Summary: Backup

A

Aurora backs up your cluster volume automatically and retains restore data for the length of the backup retention period

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
24
Q

Aurora Summary: Serverless

A

for unpredictable / intermittent workloads, no capacity planning

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Aurora Summary: Multi-Master
for continuous writes failover (high write availability)
26
Aurora Summary: Aurora Global
up to 16 DB read instances in each region, <1 sec. storage replication
27
Aurora Summary: Machine Learning
perform ML using SageMaker & Comprehend on Aurora
28
Aurora Summary: Database cloning
new cluster from existing one, faster than restoring a snapshot
29
Aurora Summary: Use Case
same as RDS (Store relational datasets (RDBMS / OLTP), perform SQL queries and transactions), but with less maintenance, more flexibility, more performance, and more features.
30
ElastiCache Summary: Type
Managed Redis / Memcached (similar offering as RDS, but for caches)
31
ElastiCache Summary: Storage
In-memory data store, sub ms latency
32
ElastiCache Summary: Provisioning
Must provision an EC2 instance type
33
ElastiCache Summary: Clustering
Support for clustering (Redis), and Multi AZ, Read Replicas (sharding)
34
ElastiCache Summary: Security
IAM, Security Groups, KMS, Redis Auth
35
ElastiCache Summary: Backup
Backup, Snapshot, Point-in-time restore
36
ElastiCache Summary: Maintenance
Managed and Scheduled Maintenance
37
ElastiCache Summary: Caveats
Requires the application code to be changed to leverage ElastiCache
38
ElastiCache Summary: Use Case
Key / Value store, Frequent reads, less writes, cache results for DB queries, store session data for websites. CANNOT USE SQL.
39
Dynamo DB Summary: Type
AWS proprietary tech, managed serverless NoSQL database, ms latency.
40
Dynamo DB Summary: Capacity
Provisioned capacity with OPTIONAL auto-scaling, or on-demand capacity.
41
Dynamo DB Summary: Options
Can replace ElastiCache as a key / value store (storing session data for example using a TTL feature) to expire a row after a specific amount of time
42
Dynamo DB Summary: Availability
Multi AZ by default, Read and write are decoupled, transaction capability.
43
Dynamo DB Summary: Clustering
DAX (DynamoDB Accelerator) cluster for read cache, microsecond read latency
44
Dynamo DB Summary: Security
Security, authentication, and authorization through IAM
45
Dynamo DB Summary: Event Processing
DynamoDB streams to integrate with AWS Lambda, or Kinesis Data Streams
46
Dynamo DB Summary: Features
Global Table Feature, active-active across regions setup.
47
Dynamo DB Summary: Backup
Automated backups up to 35 days with PITR (restore to a new table), or on-demand backups.
48
Dynamo DB Summary: Export
Export to S3 without using Read Capacity Units (RCU) within the PITR window, and import from S3 without using Write Capacity Units into a new table.
49
Dynamo DB Summary: Use Case
Great to rapidly evolve schemas. Serverless app development (small documents 100s KB), distributed serverless cache, NO SQL QUERY LANGUAGE AVAILABLE.
50
S3 Summary: Type
Key / Value store for objects, great for big objects, not great for many small objects.
51
S3 Summary: Provisioning
Serverless, scales infinitely. Max object size is 5 TB. Versioning capabilities.
52
S3 Summary: Storage
Tiers: S3 standard, S3 Infrequent Access (IA), S3 Intelligent Tiering, S3 Glacier + lifecycle policy.
53
S3 Summary: Features
Versioning, Encryption, Replication, MFA-Delete, Access Logs
54
S3 Summary: Security
IAM, Bucket Policies, ACL, Access Points, Object Lambda, CORS, Object / Vault Lock
55
S3 Summary: Encryption
SSE-S3, SSE-KMS, SSE-C, client-side, TLS in transit, default encryption
56
S3 Summary: Batch
batch operations on objects using S3 Batch, listing files using S3 inventory.
57
S3 Summary: Performance
Multi-part upload, S3 Transfer Acceleration to transfer from one region to another, and S3 Select to retrieve only the data you need.
58
S3 Summary: Automation
S3 Event Notifications (SNS, SQS, Lambda, EventBridge)
59
S3 Summary: Use Cases
Static files, key / value store for big files, website hosting
60
DocumentDB Summary: Type
same for MongoDB (NoSQL database), used to store query and index JSON data
61
DocumentDB Summary: Provisioning
Similar "deployment concepts" as Aurora.
62
DocumentDB Summary: Availability
Fully Managed, highly available, with replication across 3 AX
63
DocumentDB Summary: Storage
Automatically grows in increments of 10 GB, up to 64 TB
64
DocumentDB Summary: Capacity
Automatically scales to workloads with millions of requests per second.
65
Neptune Summary: Type
Fully Managed graph database, e.g.: A popular graph data set would be a social network. Users have friends, posts have comments, comments have likes from users, users share and like posts...
66
Neptune Summary: Availability
Available across 3 AZ, up to 15 read replicas. Highly available replications across AZs
67
Neptune Summary: Capacity
Build and run applications with highly connected datasets - optimized for complex and hard queries.
68
Neptune Summary: Storage
Can store up to billions of relations, and query the graph with ms latency.
69
Neptune Summary: Use Case
Great for knowledge graphs (Wikipedia), fraud detection, recommendation engines, and social networking.
70
Keyspaces for Apache Cassandra Summary: Type
Apache Cassandra is an open-source NoSQL distributed database
71
Keyspaces for Apache Cassandra Summary: Provisioning
Managed Apache Cassandra-compatible DB service. Serverless, Scalable, highly available, FULLY MANAGED by AWS.
72
Keyspaces for Apache Cassandra Summary: Capacity
Auto-scales tables up/down based on application traffic. On-demand mode, or provisioned mode with autoscaling.
73
Keyspaces for Apache Cassandra Summary: Availability
Tables are replicated 3 times across multiple AZs
74
Keyspaces for Apache Cassandra Summary: Features
Uses Cassandra Query Language (CQL)
75
Keyspaces for Apache Cassandra Summary: Performance
Single digit ms latency at any scale, Thousands of requests per second.
76
Keyspaces for Apache Cassandra Summary: Storage
Encryption, backup, and PITR (Point-in-Time Recovery) up to 35 days
77
Keyspaces for Apache Cassandra Summary: Use Case
Store IoT devices info, time-series data, and generally any time you see Cassandra think of Keyspaces.
78
QLDB Summary: Type
A ledger is a book for recording financial transactions.
79
QLDB Summary: Provisioning
Fully Managed, Serverless, Highly available with replication across 3 AZs
80
QLDB Summary: Purpose
Used to review history of all changes made to your application data over time.
81
QLDB Summary: Features
Immutable system, no entry can be removed or modified. Cryptographically verifiable.
82
QLDB Summary: Performance
2-3x better performance than common ledger blockchain frameworks, can manipulate data using SQL
83
QLDB Summary: Differences
Difference from Amazon Managed Blockchain: NO DECENTRALIZATION COMPONENT, in accordance with financial regulation rules.
84
QLDB Summary: Use Case
Anytime you see financial transactions and Ledger.
85
Timestream Summary: Type
Time-series DB
86
Timestream Summary: Provisioning
Fully Managed, Fast, Scalable, Serverless. Automatically scales up / down to adjust capacity.
87
Timestream Summary: Performance
Store and analyze trillions of events per day. Thousands of times faster, and 1/10th the cost of Relational Databases for time-series data.
88
Timestream Summary: Features
Scheduled queries, multi-measure records, SQL compatibility. Built in time series analytic functions (helps identify patterns in data in near real time)
89
Timestream Summary: Storage
Data storage tiering: recent data kept in memory, historical data kept in cost-optimized storage.
90
Timestream Summary: Encryption
Encryption in transit and at rest.
91
Timestream Summary: Use Case
IoT apps, operational applications, real-time analytics
92
Timestream Summary: Architecture
Data stream sent into Timestream, and send to QuickSight, SageMaker, Grafana, any JDBC connection.