• Amazon Aurora • Amazon DynamoDB • A database is a collection of organized data that is stored electronically in a computer system. The purpose of a database is to make data easier to manage and access. Unmanaged versus managed services Challenges of relational databases • Server maintenance and energy • Software installation and patches • Database backups and high availability • Limits on scalability • Data security • Operating system (OS) installation and patches Managed services responsibilities Amazon RDS in a virtual private cloud (VPC) High availability with Multi-AZ deployment (2 of 2) Amazon RDS read replicas Use cases Mysql connect with mysql workbench Aurora • Aurora is proprietary technology from AWS. • Mysql and Postgres are both supported as Aurora DB. • Storage automatically grows increments of 10 GB to 64 TB. • Aurora cost more than RDS(20 % more) but more efficient. • Not in the free tier. High Performance and Scalability • Aurora is “ AWS cloud optimized” and claims 5X performacne improvement over Mysql on RD • 3X performacne improvement over Postgre on RDS. High Availability and durability • 99.99% Availability. • Replicating 6 copies of data across 3AZ and backup data continously to Amazon S3. • Transparently recovers from physical storage failure. • Instance backup takes lessthan 30 seconds without any dataloss Highly Secure • Amazon VPC used for network isolation. • Data transfer happened by AWS KMS key encryption( snaphot / backup) Mysql & Postgres Compatible • Easy migrate from this to Amazon Aurora. • Import/Export completely manageable. Fully Managed • Hardware provisioning • Software patching • DB setup • Configuration. • Backup Benefits High availability Resilient design (Ex.quickly recover from disruptions like natural disasters) Amazon DynamoDB Relational versus non-relational databases Relational Databases (RDBMS)
• Examples in AWS: Amazon RDS (MySQL,
PostgreSQL, MariaDB, Oracle, SQL Server), Amazon Aurora. • Data Structure: Data is organized into tables with predefined schemas (rows and columns), supporting structured data and relational models. • Schema Requirements: Requires a fixed schema, meaning data must conform to a defined structure. Non-Relational Databases (NoSQL)
• Examples in AWS: Amazon DynamoDB,
Amazon DocumentDB (MongoDB-compatible), Amazon Keyspaces (for Apache Cassandra). • Data Structure: Flexible data models like key- value, document-based, wide column, or graph. Data is typically stored in a denormalized format, reducing the need for joins. DynamoDB Streams • DynamoDB Streams writes stream records in near-real time so that you can build applications that consume these streams and take action based on the contents. Accessing DynamoDB and DynamoDB Streams