Please enable JavaScript.

Coggle requires JavaScript to display documents.

Database (Type (RDS (OLTP - Online Transaction Processing - query)…

- - - - Features
        
        2 copies of your data is contained in each AZ, with minimum of 3 AZ => 6 copies or your data
        
        Replica
        
        Aurora Replicas
        
        Automatically failover is available
        
        MySQL Replicas
        
        automated backup is turned on by default , backup & snapshot does not impact database performance
        
        can take snapshots and share with other AWS accounts
        
        is a MySQL-compatible, 5 times better performance than MySQL
    - - Multi-AZ
        
        for disaster recovery
        
        You can force failover from one AZ to another by rebooting RDS instance
      - Read Replicas
        
        Increase performance
        
        Must have backup turns on to create Read Replica
        
        Can be multi AZ, can be promoted to master (when happen it will break read replica)
        
        Can be Aurora or MySQL
      - RDS run on VM, however cant login to these OS => patching RDS OS is Amazon's responsibility
      - RDS is not serverless (except Aurora serverless)
      - Backup
        
        Automated Backup (via schedule maintenance window)
        
        Database Snapshot (manually)
  - - - Stored on SSD, super fast
      - Spread across 3 geographically distinct data centers
      - Read type
        
        Eventual Consistent Read (default, after one second)
        
        Strongly Consistent Read (immediately)
      - Missing other features, check LinuxAcademy Notes on computer
    - - Read Capacity Unit
        
        one strongly consistent read per second, or two eventually consistent reads per second, for an item up to 4 KB in size
        
        item size = 6KB => 2 strong read, 1 eventual read
      - Write Capacity Unit
        
        one write per second for an item up to 1 KB in size
        
        item size = 2KB => 2 write unit
  - - - Only available in one AZ
      - Backup
        
        Enable by default with 1 day retention period, max 35 days
        
        always attempt to maintain at least 3 copies of your data (original & replica on compute node, backup in S3)
        
        async replica your snapshots to S3 in another region for DR
      - can be configured as
        
        Single Node (160Gb)
        
        Multi-Node
        
        Leader Node (manage client connections & receive queries)
        
        Compute Node (store data, perform queries & computation) - up to 128 Compute Nodes
      - Advanced Compression
        
        Columnar compression (compress by column because same type data so can be compressed more)
      - Massive Parallel Processing (MPP)
        
        automatically distributes data & query load across all nodes
      - Price
        
        Compute Node Hours (1 unit per node per hour)
        
        Leader nodes wont be charged
        
        Backup
        
        Data transfer
      - is used for business intelligence
  - - - scale horizontally
    - - multi-AZ
      - can do backup & restore