GridDB Enterprise Edition is a more robust version of the open source GridDB Community Edition that has been fully tested against production workloads, includes additional enterprise features for a more secure deployment of your data storage, and a comprehensive technical support with the best SLA suitable for mission critical applications.

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.

In GridDB, there is no explicit primary node. The primary node has not yet been determined when the database cluster is started, and the primary node will be absent in the event of a primary node failure. At this time, the election between nodes and the cluster dynamically determine the primary. Therefore, there is no single point of failure (SPOF).

The data placement information of the container is shared by each node and client. Therefore, the client directly accesses the data by referring to the data arrangement information on the client side. As a result, the management server and mediation server, which are single contact points (SPOCs) located between the client and the DB server, are eliminated. As a result, costs such as communication and data conversion processing have been significantly reduced, achieving high availability and high performance at the same time.

Node failure, node expansion, and long-term operation can cause imbalances in data placement between nodes. In order to prevent performance degradation, always improve the data arrangement between nodes so that the load is not concentrated on a specific node. To maintain availability, you need to keep a copy of your data.

When the autonomous data distribution algorithm (ADDA) detects data imbalance, it autonomously decides the relocation plan for the database server of data and its copy, and perform high-speed data transfer between the servers. 

GridDB Enterprise Edition is equipped with extra layer of security. The communication path between GridDB cluster and client is protected by SSL.  In addition LDAP authentication is supported, enabling centralized management of authentication information.

GridDB Enterprise Edition comes with an integrated operation GUI (gs_admin) out of the box. gs_admn includes admin functionalities such as cluster monitoring, performance tuning, and fault monitoring. In addition import/export tool, online backup and rolling upgrade are supported.

Get access to GridDB technical support experts and we will be there in every step of your journey from development to production release.