DBMS > CockroachDB vs. GridGain vs. Informix vs. SQLite

System Properties Comparison CockroachDB vs. GridGain vs. Informix vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

CockroachDB is a distributed database architected for modern cloud applications. It is wire compatible with PostgreSQL and backed by a Key-Value Store, which is either RocksDB or a purpose-built derivative, called Pebble.

GridGain is an in-memory computing platform, built on Apache Ignite

A secure embeddable database from IBM, positioned besides IBM Db2 as a relatively low-cost product optimized for OLTP and Internet of Things data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Since Version 12.10 support for JSON/BSON datatypes compatible with MongoDB

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS

with Informix TimeSeries Extension

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	4.74
Rank	#67	Overall
	#36	Relational DBMS

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	16.32
Rank	#35	Overall
	#21	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

www.cockroachlabs.com

www.gridgain.com

www.ibm.com/products/informix

www.sqlite.org

Technical documentation

www.cockroachlabs.com/docs

www.gridgain.com/docs/index.html

informix.hcldoc.com
www.ibm.com/support/knowledgecenter/SSGU8G/welcomeIfxServers.html

www.sqlite.org/docs.html

Developer

Cockroach Labs

GridGain Systems, Inc.

IBM, HCL Technologies

Effective May 1st, 2017, HCL took on development, technical support, and product management teams, and works jointly with IBM on product strategy, marketing, and sales.

Dwayne Richard Hipp

Initial release

2015

2007

1984

2000

Current release

24.1.0, May 2024

GridGain 8.5.1

14.10.FC5, November 2020

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

Apache 2.0, commercial license available

commercial, open source

commercial

free developer edition available

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, C++, .Net, Python, REST, SQL

C, C++ and Java

Server operating systems

Linux
macOS
Windows

Linux
OS X
Solaris
Windows
z/OS

AIX
HP-UX
Linux
macOS
Solaris
Windows

server-less

Data scheme

dynamic schema

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Since Version 12.10 support for JSON/BSON datatypes

yes

not rigid because of 'dynamic typing' concept.

XML support

Some form of processing data in XML format, e.g. support for XML data structures, and/or support for XPath, XQuery or XSLT.

yes

Secondary indexes

yes

SQL

Support of SQL

yes, wire compatible with PostgreSQL

ANSI-99 for query and DML statements, subset of DDL

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

JDBC
JSON API

MongoDB compatible
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C#
C++
Clojure
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes (compute grid and cache interceptors can be used instead)

yes

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

horizontal partitioning (by key range)

all tables are translated to an ordered KV store and then broken down into 64MB ranges, which are then used as replicas in RAFT

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

yes (replicated cache)

Multi-source replication
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

User concepts

Access control

Role-based access control

Role-based access control
Security Hooks for custom implementations

Users with fine-grained authentication, authorization, and auditing controls

More information provided by the system vendor

We invite representatives of system vendors to contact us for updating and extending the system information,
and for displaying vendor-provided information such as key customers, competitive advantages and market metrics.