AWS RDS Aurora
AWS Aurora is a relational engine that combines high-end commercial databases’ speed and reliability with open-source databases’ simplicity and cost-effectiveness.
Aurora is a fully managed, MySQL- and PostgreSQL-compatible, relational database engine i.e. Applications developed with MySQL can easily switch to Aurora.
Aurora provides up to 5x the performance of MySQL without any modifications to most MySQL applications
Aurora PostgreSQL offers up to 3x the performance of PostgreSQL
RDS manages Aurora databases. This includes time-consuming tasks like provisioning, patching and recovery, failure detection, repair, and recovery.
Aurora storage will automatically increase based on database usage. It will grow from 10GB to 64TiB per 10GB increments without any impact on database performance. Aurora DB ClustersAurora DB ClustersAurora DB ClustersAurora DB Cluster consists of one or several DB instances and a volume that manages the data.
An Aurora cluster volume is a virtual storage volume that spans multiple AZs. Each AZ has a copy the DB cluster data.
An Aurora DB cluster is made up of two types of DB instances: Primary DB instanceSupports read-and-write operations and performs all data modifications to the cluster volume.
Each Aurora DB cluster is assigned one primary DB instance.
Aurora ReplicaConnects to a same storage volume and supports only read operations.
Each Aurora DB cluster may have up to 15 Aurora Replicas, in addition to the primary DB instance.
Replicas can be found in separate AZs, which ensures high availability
Aurora automatically fails to an Aurora Replica if the primary DB instance is unavailable.
You can specify failover priority for Aurora Replicas.
Aurora Replicas are also able to offload read workloads from a primary DB instance
Aurora multi-master clusters all DB instances have read/write capabilities with no difference between replica and primary.
Aurora is a cluster of DB instance instances, instead of a single instance
Endpoint refers the intermediate handler that specifies the host name and port to connect to the cluster.
Aurora uses the endpoint mechanism for these connections. Cluster endpoint
The cluster endpoint (or writer) for an Aurora DB Cluster connects to the primary DB instance for that DB Cluster.
Cluster endpoint is the only one capable of performing write operations such DDL statements and read operations.
Each Aurora DB Cluster has one primary DB instance and one cluster endpoint.
Cluster endpoint provides failover support to read/write connections to the DB-cluster. Aurora automatically switches to a new primary DB in the event that the primary DB instance fails. The failover ensures that the DB cluster continues to service connection requests to the cluster endpoint using the new primary DB instance. There is minimal interruption to service.
An Aurora DB Cluster Reader Endpoint provides load-balancing support for read only connections to the DB cluster.
For read operations such as queries, use the reader endpoint.
The overhead of the primary instance is reduced by the reader endpoint processing the statements on the Aurora Replicas read-only.
Each cluster of Aurora DB clusters has one reader endpoint.
Custom endpoint
A custom endpoint for an Aurora cluster is a set or instances of DB that you select.
Aurora does load balancing and selects one of the instances within the group to handle the connection.
An Aurora DB cluster does not have any custom endpoints unless one is created. Each provisioned Aurora cluster can have up to five custom endpoints.
Aurora Serverless clusters doesn’t support custom endpointsInstance endpoint
An instance endpoint connects with a specific DB instance in an Aurora cluster and provides