GridDB
Community Edition

GridDB is an open source database designed to store large amount of time series data in real time.

GridDB
Enterprise Edition

The best way to run GridDB in a production environment. Equipped with advanced security and professional support.

 
GridDB Cloud

Fully managed GridDB as-a-service deployed on the cloud. Our experts take care of troublesome database maintenance for you.

Features

GridDB is built from the ground up to store huge amount of time series data generated by IoT devices in real time. IoT, Big Data and Cyber Physical System require a data storage capable of ingesting data at high velocity, and elastically scale to the petabyte level while maintaining the same performance, all done without any downtime. 

GridDB’s NewSQL architecture utilizes the fast NoSQL interface for data ingestion and the reliable SQL interface to accelerate application development. Management of  ever-growing time series data is made easy with GridDB’s time series data retention policy, aggregation and interpolation functions. With the added security features, GridDB ensures that your data is safe and secure.

1. Time Series Data Management Done Efficiently

The Key Container data model of GridDB extends the typical NoSQL Key-Value store. The Key Container model represents data in the form of collections that are referenced by keys. The key and container are rough equivalents of the table name and table data in Relational Databases (RDB). Data modeling in GridDB is easier than with other NoSQL databases as we can define the schema and design the data similar to that of an RDB.

The Key Container model allows high speed access to data through Java and C APIs. Data in GridDB can be queried through SQL. Additionally, basic search through the WHERE command and high speed conditional search operations through indexing offer a great advantage for applications that rely on faster search. GridDB supports transactions, including those with plural records from the application. Transactions in GridDB guarantee ACID (Atomicity, Consistency, Isolation, and Durability) at the container level.

2. Petabyte-Scale Performance for Big Data System

GridDB incorporates various architectural ingenuity to achieve high speed.

For example, GridDB has developed an event-driven method that continuously executes asynchronous data processing, allocates memory and database files to be occupied by each CPU core thread, and eliminates the waiting for exclusive and synchronous processing.

GridDB also localizes the data that your application needs access to, with a unique time-series data placement technology that places the main data in the same block as much as possible to process large amounts of data. By setting memory aggregation hints according to the access pattern and access frequency of the application, the memory area can be effectively used and memory miss hits can be reduced.

3. Highly Available and Reliable

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 primary 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.

4. Improve Developers Productivity

GridDB provides the high speed NoSQL interface as well as the standard SQL interface. NoSQL interface can perform operations such as CRUD (Register, Update, Delete, and Reference) on the record identified by key pair.

In addition, various interfaces are available so that GridDB can be accessed though a variety of  languages such as Java, C, Python, Go, and Node.js. Container in GridDB is similar to the concept of table in RDB, and it can be accessed through the SQL interface. GridDB supports standard RDB connection interface such as ODBC and JDBC.

Different products for your needs

Item
Functionality

GridDB
Community Edition

GridDB
Enterprise Edition

GridDB Cloud
Support
 
Professional Service
 
Data Management
Time Series Container
Collection Container
Index
Data Affinity
Table Partitioning
Query Language
TQL
SQL
NoSQL Interface
Java
C
NewSQL(SQL) Interface
JDBC
ODBC  
WebAPI  
Time Series Data
Time Series Analysis
Expiry Release (Data Retention)
 
Long-Term Archive
 
Clustering
Cluster Configuration
 
Distributed Data Management
 
Replication
 
Administration
Rolling Upgrade
   
Online Backup
 
Export/Import
 
Operation Management GUI
 
Operation Command
 
Security
Data-In-Transit (TLS/SSL)
 
Authentication (LDAP)
   
On Premise On Premise  
Cloud Service Cloud Service    
Item
Functionality

GridDB
Community Edition

GridDB
Enterprise Edition

GridDB Cloud
Support
 
Professional Service
 
Data Management
Time Series Container
Collection Container
Index
Data Affinity
Table Partitioning
Query Language
TQL
SQL
NoSQL Interface
Java
C
NewSQL(SQL) Interface
JDBC
ODBC  
WebAPI  
Time Series Data
Time Series Analysis
Expiry Release (Data Retention)
 
Long-Term Archive
 
Clustering
Cluster Configuration
 
Distributed Data Management
 
Replication
 
Administration
Rolling Upgrade
   
Online Backup
 
Export/Import
 
Operation Management GUI
 
Operation Command
 
Security
Data-In-Transit (TLS/SSL)
 
Authentication (LDAP)
   
On Premise On Premise  
Cloud Service Cloud Service    

Download GridDB Community Edition here

Notes

The following condition apply to Community Edition:

・Server

 - Multi nodes configuration is not available.

 - The default build environment has the trigger function disabled. Trigger function is not included in packages other than CentOS.

・Administration

 - Operation commands are limited.

 - For example, full backup, differential / incremental backup, archive storage, etc. cannot be used.

・C client(C API)

 - Spatial data is not supported.