Cloud-based High Availability DBMS Configuration
Cloud-based High Availability DBMS Configuration
Overview
In a cloud environment, the stability of the database is a crucial factor. To ensure data stability and service continuity, Samsung Cloud Platform DBaaS provides a high availability configuration with synchronous replication, which can guarantee availability even in an enterprise environment.
Samsung Cloud Platform provides a database service based on the optimal high availability architecture, backed by technical analysis of various database high availability configurations. You can choose the optimal configuration according to the type of database (RDBMS, NoSQL, etc.), and this document explains the high availability configuration for MySQL and PostgreSQL.
Architecture Diagram
Architecture Configuration and Operation
Client Access
- Clients access the database service through a Virtual IP (VIP) or DNS query.
- Before creating a database service, users must configure a VPC in advance, and the database is created based on that VPC.
Active Node Designation
- The VIP or DNS holds the current Active Node information in the duplicated database configuration and forwards user requests to the Active Node.
Data Synchronization
- Data created or changed in the Active Database is recorded in Block Storage and synchronized with the Standby Node.
Service Continuity in Case of Failure
- Even if a problem occurs in the Active or Standby Node, the service can be continuously provided without data loss through the synchronized Block Storage data.
Security Settings
- To access the created database, set the DB Port and Target IP in the Security Group.
Use Cases
Utilization in Various Enterprise Solutions
- MySQL (DBaaS) and PostgreSQL (DBaaS) databases can be used in various business solutions such as logistics, RPA, and workflow automation.
- Infrastructure duplication and high availability configuration provide uninterrupted services.
- In case of physical or logical failures (e.g., Hang, data loss), high availability-based Failover ensures service continuity.
Service Continuity in Case of Infrastructure or DB Failure
- In case of infrastructure failures (e.g., virtual machine, OS, network, storage) or database failures (e.g., Hang, DB process error), Failover within 1-2 minutes ensures service continuity.
Pre-requisites
None
Limitations
- Although the high availability database provides automatic Failover functionality, additional checks are required to ensure system normality after Failover in case of failure.
Considerations
- Depending on service importance, you can choose between a single Virtual Server-based configuration or a duplicated high availability database configuration.
- Duplicated databases utilize two Virtual Servers and storage space, resulting in increased costs compared to single configurations, and data synchronization replication may cause some performance degradation.
- It is recommended to select the optimal option through testing and performance verification before using the database.
Related Services
This is a list of Samsung Cloud Platform services related to the functionality or configuration described in this guide. Refer to this list when selecting and designing services.
| Service Group | Service | Detailed Description |
|---|---|---|
| Database | EPAS(DBaaS) | A service that allows easy creation and management of EPAS in a web environment |
| Database | PostgreSQL(DBaaS) | A service that allows easy creation and management of open-source PostgreSQL in a web environment |
| Database | MariaDB(DBaaS) | A service that allows easy creation and management of MariaDB, which is highly compatible with MySQL |
| Database | MySQL(DBaaS) | A service that allows easy creation and management of the powerful open-source relational database MySQL |