관계형 DB(RDB)

관계형 DB란?

관계형 데이터베이스는 데이터 진입점의 수집과 이들 사이의 관계에 초점을 맞춘 데이터베이스로 분류됩니다.

관계형 DB를 선택할 시기를 어떻게 알 수 있습니까?

데이터 진입점 간의 관계에 대한 지식이 있고 테이블의 데이터를 나타내는 복잡하지 않은 작업 과정이 있는 경우 RDB가 최선의 선택입니다.

일부 산업 RDB 사용 사례는 무엇입니까?

기존 애플리케이션,

전사적 자원 관리(ERP),

고객관계관리(CRM),

전자상거래

리프트 앤 시프트

이제 RDB에 대한 일반적인 아이디어를 얻었으므로 계속해서 더 깊이 파고들어 AWS RDB 리소스를 탐색하고 구축해 보겠습니다.

아마존 RDS

아마존 오로라

아마존 레드시프트

아마존 RDS란?

Amazon Relational Database Service (Amazon RDS) is a managed service that makes it easy to set up, operate, and scale.

A relational database in the cloud. It provides cost-efficient and resizable capacity, while managing time-consuming database administration tasks, freeing you up to focus on your applications and business.

Amazon RDS는 다음과 같은 친숙한 SQL 기능에 대한 액세스를 제공합니다.

MySQL

마리아DB

신탁

SQL 서버

PostgreSQL 데이터베이스

아마존 오로라는 무엇입니까?

Amazon Aurora is a modern relational database service offering performance and high availability at scale, fully open-source MySQL- and PostgreSQL-compatible editions, and a range of developer tools for building serverless and machine learning (ML)-driven applications.

아마존 레드시프트란?

Amazon Redshift is a fully managed, scalable cloud data warehouse that accelerates your time to insights with fast, easy, and secure analytics at scale.

이 3개의 RDB에 대한 몇 가지 중요한 특성을 살펴보겠습니다.

아마존-RDS

Performance:

- General Purpose Storage : 3 IOPS * each GB.
- Burst capacity: 3,000 IOPS
- Provisioned IOPS storage:  40,000 IOPS *  each RDS instance. 
- Formula: (Credit balance)
Burst duration =  ---------- (Burst IOPS) - 3*(Storage size in GiB)

Scalability:

- Horizontal
- Vertical 

Availability:

- Multi-AZ service level agreement: 99.95% up every month

Security:

- Encryption of data at rest using KMS
- Encryption of data in transit using SSL/TLS
- Access Control using IAM
- Network Isolation and Database Firewall using VPC and industry-standard encrypted IPSec VPN
- Database activity streams beyond external security threats providing a real-time data stream of the database activity in 
your relational database

아마존-오로라

Performance:

- 5x throughput of standard MySQL
- 3x of standard PostgreSQL
- Auto-scales up to 128 TB per database instance

Scalability:

- The minimum storage is 10 GB
- Automatically grow, up to 128 TB, in 10 GB increments with no impact on database performance
- Scale out up to 15 read replicas

Availability:

- Fault tolerant
- Self-healing storage
- Automatically divides your database volume into 10 GB segments spread across many disks
- Six copies of data across three AZ's
- Continuous backup to Amazon S3

Security:

- Uses SSL (AES-256) to secure the connection between the database instance and the application
- Network isolation
- Encryption at rest and in transit 

Amazon-Redshift

Performance:

- Massively parallel processing
- Columnar data storage
- Data compression
- Query optimizer
- Result caching
- Compiled code
- 10x better performance than traditional databases
- Automatic Table Optimization (ATO)
- ATO increases cluster performance by 24% and 34% using the 3 TB and 30 TB versus a cluster without ATO 

Scalability:

- Petabyte-scale data warehouse

Availability:

- The cluster node is replaced automatically in case of node failure detection
- Data is backup into S3

Security:

- Built-in AWS IAM integration
- Identity federation for single-sign-on (SSO)
- MFA
- Column level access control
- Row-level security
- Encrypts and keeps your data secure in transit and at rest

이제 고려해야 할 몇 가지 제한 사항을 살펴보겠습니다.

아마존 RDS:

- Read replicas per region: 5 
- Reserved DB instances per region: 40 
- Rules per security group per region: 20 
- Security groups per region: 25 
- Security groups (VPC) per region: 5 

아마존 레드시프트:

- AWS accounts that you can authorize to restore a snapshot per snapshot: 20 
- Concurrency level (query slots) for all user defined manual WLM queues: 50 
- Concurrency scaling clusters: 10 
- Nodes: 200 
- Schemas in each database per cluster: 9,900 
- Security groups: 20 
- Snapshots: 20 

아마존 오로라:

- Authorizations per DB security group per region: 20 
- Custom engine versions per region: 40 
- DB cluster parameter groups per region: 50 
- DB clusters per region: 40 
- DB instances per region: 40 
- DB subnet groups per region: 50 
- Data API HTTP request body size per region: 4 MGB 

이러한 제한 사항 중 일부는 조정 가능하고 다른 제한 사항은 조정할 수 없습니다.

아, 맞다 구축 중입니다 👷 이제 Terraform을 사용하여 이 3개의 데이터베이스를 구축하겠습니다.



Find the Terraform repo and directions for this project here

Terraform 코드 이전:

#---aurora/main--

resource "aws_rds_cluster_instance" "cluster_instances" {
  count              = 1
  identifier         = "aurora-cluster-example-${count.index}"
  cluster_identifier = aws_rds_cluster.my_rds.id
  instance_class     = "db.r4.large"
  engine             = aws_rds_cluster.my_rds.engine
  engine_version     = aws_rds_cluster.my_rds.engine_version
}

resource "aws_rds_cluster" "my_rds" {
  cluster_identifier = "aurora-cluster-example"
  availability_zones = ["us-west-2a", "us-west-2b", "us-west-2c"]
  database_name      = "USES-YOUR-OWN-DB-NAME-HERE"
  master_username    = "username"
  master_password    = "Always_use_complex_password"
}

도표



참조:

https://aws.amazon.com/rds/features/security/ 

https://aws.amazon.com/redshift/faqs/ 

https://aws.amazon.com/rds/aurora/faqs/ 

https://docs.aws.amazon.com/AmazonRDS/latest/UserGuide/CHAP_Limits.html 

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Limits.html 

https://docs.aws.amazon.com/AmazonRDS/latest/AuroraUserGuide/CHAP_Limits.html