Amazon Aurora HA and DR design patterns for global resilience (DAT304)

Here is a detailed summary of the key takeaways from the video transcription in Markdown format:

Resilience and High Availability

  • Resilience: The ability of a workload to recover from infrastructure changes, service disruptions, and mitigate disruptions.
  • Resilience is supported by two pillars:
    1. Availability: The proportion of time a workload is available for use, usually expressed as a historical measure over a period of time.
    2. Disaster Recovery: Techniques and strategies used to recover a workload in the case of a disaster event, measured by Recovery Time Objective (RTO) and Recovery Point Objective (RPO).

Aurora Resilience Patterns

  1. Minimal Configuration:

    • Single database instance in one Availability Zone with Aurora storage across three Availability Zones.
    • Provides durability and availability, but single point of failure.
  2. Continuous Incremental Backup:

    • Aurora continuously backs up database changes to Amazon S3.
    • Allows point-in-time recovery within a retention period.
  3. Aurora Clones:

    • Create clones of the production database for testing and development.
    • Clones only store changes, reducing storage costs.
  4. Multi-AZ Configuration:

    • Add a secondary instance in a different Availability Zone for failover.
    • Provides higher availability with 30-second failover time.
  5. Read Replicas:

    • Add read replicas to offload read traffic and increase read throughput.
    • Replicas are kept up-to-date with the primary instance.
  6. Failover Tiers:

    • Configure failover tiers to prioritize which instances to fail over to.
    • Ensures the failover instance can handle the workload.
  7. Connection Management:

    • Use the AWS Advanced JDBC driver or Aurora Proxy to handle connection management and failover.
    • Improves application resilience to topology changes.

Global Resilience

  1. Cross-Region Backups:

    • Take backups of the database in one region and copy them to another region.
    • Provides disaster recovery, but higher RPO (data loss) and RTO (recovery time).
  2. Aurora Global Database:

    • Asynchronous replication of data across multiple AWS Regions.
    • Provides low RPO (sub-second) and RTO (under 15 minutes).
    • Can have symmetric configurations for faster failover.
  3. Read Resilience:

    • Run read-only workloads in multiple regions for lower latency.
    • Use write forwarding to handle writes transparently.
  4. Consistency Options:

    • Session-level consistency: Read your own writes.
    • Eventual consistency: Faster reads, but writes may not be immediately visible.
    • Global read visibility: Consistent reads across all regions, but higher latency.
  5. Cross-Account Backups:

    • Take backups and store them in a separate AWS account for added protection.

Journey to Global Resilience

  1. Minimal Configuration
  2. Continuous Incremental Backup
  3. Aurora Clones
  4. Multi-AZ Configuration
  5. Read Replicas
  6. Failover Tiers
  7. Connection Management
  8. Cross-Region Backups
  9. Aurora Global Database
  10. Read Resilience
  11. Consistency Options
  12. Cross-Account Backups

Your Digital Journey deserves a great story.

Build one with us.

Cookies Icon

These cookies are used to collect information about how you interact with this website and allow us to remember you. We use this information to improve and customize your browsing experience, as well as for analytics.

If you decline, your information won’t be tracked when you visit this website. A single cookie will be used in your browser to remember your preference.

Talk to us