Native Database Replication
Most modern enterprise-grade databases have native support for clustering and data replication. Iotellect Server may benefit from native database clustering by auto-switching between primary and failover database nodes, while the database engine manages data replication between nodes.
The following database engines compatible with Iotellect Server support failover clustering technology:
- Oracle
- MySQL
- Microsoft SQL Server
- PostgreSQL
Pros and Cons
Pros:
- Data is replicated to all database cluster nodes to ensure reliability.
- Native replication guarantees fast and efficient data replication between nodes.
- When a database cluster node temporarily fails, the subsequent synchronization of data between failed node and other nodes is performed by the DBMS engine with minimal overhead.
Cons:
- Building a native database cluster can be a complex challenge.
- Iotellect Server JDBC (database) driver must be configured to auto-switch to failover database servers.
Configuration
Below is the list of configuration changes required to set up native database clustering.
Database Servers
- Refer to your database server documentation for details on how to build a cluster.
Master Iotellect Server
- If your master server is not yet configured to work with the clustered database, switch it to your database server.
- Refer to your JDBC driver documentation for details on how to configure the addresses of failover servers. In most cases this is performed by specifying failover server addresses in the Database URL.
Failover Iotellect Server
- Use exactly the same database configuration as on the Master server.
Was this page helpful?