GridDB Community Edition supports a single node configuration that is enough for most cases. For mission critical applications that require high availability, GridDB Enterprise Edition can be scaled out through clustering. Network partitions, node failures, and maintaining consistency are some of the major problems that arise when data is distributed across nodes. Typically, distributed systems adopt Primary-Replica or ‘Peer-to-Peer’ architectures. Primary-Replica option is good at maintaining data consistency but a master node redundancy is required to avoid having a Single Point of Failure (SPOF). Peer-to-Peer, though avoids SPOF, has a huge problem of communication overhead among the nodes.
GridDB’s autonomous control cluster architecture integrates the advantages of and overcomes the disadvantages of both Primary-Replica and Peer-to-Peer styles. GridDB’s algorithms select the master node automatically among peers, and, in case of Primary node failure, operations remain intact as a new primary is appointed automatically and immediately. GridDB’s proprietary algorithms avoid the classic distributed computing problem of Split-Brain, which occurs due to cluster partition during network failures. GridDB also offers various levels of replication based on the availability requirements of the application.