DBMS > chDB vs. CockroachDB vs. GridGain vs. Microsoft SQL Server vs. SWC-DB

System Properties Comparison chDB vs. CockroachDB vs. GridGain vs. Microsoft SQL Server vs. SWC-DB

Editorial information provided by DB-Engines

Name

Description

An embedded SQL OLAP Engine powered by ClickHouse

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

Microsofts flagship relational DBMS

A high performance, scalable Wide Column DBMS

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Wide column store

Secondary database models

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

Time Series DBMS

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

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	6.15
Rank	#55	Overall
	#33	Relational DBMS

Score	1.47
Rank	#154	Overall
	#26	Key-value stores
	#72	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

github.com/chdb-io/chdb

www.cockroachlabs.com

www.gridgain.com

www.microsoft.com/en-us/sql-server

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

doc.chdb.io

www.cockroachlabs.com/docs

www.gridgain.com/docs/index.html

learn.microsoft.com/en-US/sql/sql-server

Developer

Cockroach Labs

GridGain Systems, Inc.

Microsoft

Alex Kashirin

Initial release

2023

2015

2007

1989

2020

Current release

23.1.1, May 2023

GridGain 8.5.1

SQL Server 2022, November 2022

0.5, April 2021

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0, commercial license available

commercial

restricted free version is available

Open Source

GPL V3

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

C++

Server operating systems

server-less

Linux
macOS
Windows

Linux
OS X
Solaris
Windows

Linux
Windows

Linux

Data scheme

dynamic schema

yes

schema-free

Typing

predefined data types such as float or date

yes

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

Close to ANSI SQL (SQL/JSON + extensions)

yes, wire compatible with PostgreSQL

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

yes

SQL-like query language

APIs and other access methods

JDBC

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

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Proprietary protocol
Thrift

Supported programming languages

Bun
C
C++
Go
JavaScript (Node.js)
Python
Rust

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

C#
C++
Java
PHP
Python
Ruby
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C++

Server-side scripts

Stored procedures

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

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

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

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using RAFT

yes (replicated cache)

yes, but depending on the SQL-Server Edition

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

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

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

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.