Please enable JavaScript.
Coggle requires JavaScript to display documents.
Aurora - Coggle Diagram
Aurora
Connection Endpoint
Cluster
writer endpoint
connects to the current primary DB instance
performs
write operations
DDL statements
read operations
provides failover support for read/write connections to the DB cluster
the DB cluster continues to serve connection requests to the cluster endpoint from the new primary DB instance
Custom
not supported by Aurora Serverless
represents set of DB instances choosen
up to 5 for each provisioned cluster
Reader
provides
load balancing support for
read only connections to the cluster
balances connection request among the Replicas
queries
reduces overhead on the primary instance
Instance
connects to a specific DB instance within cluster
provides direct control over connections to DB cluster
Each DB instance in a DB cluster has its own unique instance endpoint
one for each Replica
one for primary
refers to an intermediate handler
hostname
port specified
to connect to the cluster
DB Clusters
Clone
create cluster duplicates
quickly
cost-effectively
is
faster
space efficient
allocates new storage when data changes
on the source cluster
on the cloned cluster
uses
copy-on-write protocol
minimal additional space when first created
single copy of data is used by
the original
new DB clusters
consists of
one or more DB instances
type
Primary DB instance
supports read/write operations
Each DB cluster has one primary DB instance
Aurora Replica
supports only read permitions
connects to the same storage volume
high availability
replica in different AZ
failover
to a Replica in case primary unavailable
priority specified
offload workloads from primary
Aurora multi-master clusters
all DB instances have read/write capability, with no difference between primary and replica
cluster volume
manages data for DB instances
is a virtual database storage volume
spans multiple AZ
each AZ having a copy of the DB cluster data
involved by Aurora instead of a single instance
has
Cluster Endpoint
Reader Endpoint
Security
at rest also the underlying storage is encrypted
backups
snapshots
replicas inthe same cluster
SSL (AES-256)
connection between the database instance and the application
database encryption with
KMS
Encryption of existing unencrypted Aurora instances is not supported.
Create a new encrypted Aurora instance and migrate the data
Parallel Query
distribute computational load of a single query across thousands of CPUs in Aurora's storage layer
benefits
faster performance
Operational simplicity and data freshness
Transactional and analytical workloads on the same database
aurora_pq parameter
disable/enable
at level
global
session
available for the MySQL 5.6-compatible version of Aurora
is
fully managed
compatible
MySQL
5x the performance
PostgreSQL
3x
handling time consuming tasks
provisioning
patching
backup
recovery
failure detection
repair
scale storage automatically
from 10GB to 128 TiB
increment of 10 GB
no impact on db performance
Scaling
relational database engine
combines
speed
reliability
cost effective
open-source database
BackTrack
advantages respect traditional backup