DBMS > GridGain vs. SWC-DB vs. TerarkDB vs. VoltDB

System Properties Comparison GridGain vs. SWC-DB vs. TerarkDB vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

A high performance, scalable Wide Column DBMS

A key-value store forked from RocksDB with advanced compression algorithms. It can be used standalone or as a storage engine for MySQL and MongoDB

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Wide column store

Key-value store

Relational DBMS

Secondary database models

Time Series DBMS

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

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

Score	0.01
Rank	#378	Overall
	#13	Wide column stores

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Score	1.38
Rank	#156	Overall
	#72	Relational DBMS

Website

www.gridgain.com

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

github.com/bytedance/terarkdb

www.voltdb.com

Technical documentation

www.gridgain.com/docs/index.html

bytedance.larkoffice.com/docs/doccnZmYFqHBm06BbvYgjsHHcKc

docs.voltdb.com

Developer

GridGain Systems, Inc.

Alex Kashirin

ByteDance, originally Terark

VoltDB Inc.

Initial release

2007

2020

2016

2010

Current release

GridGain 8.5.1

0.5, April 2021

11.3, April 2022

License

Commercial or Open Source

commercial, open source

Open Source

GPL V3

commercial

restricted open source version available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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++

Java, C++

Server operating systems

Linux
OS X
Solaris
Windows
z/OS

Linux

Linux
OS X

for development

Data scheme

yes

schema-free

yes

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

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

SQL-like query language

yes

only a subset of SQL 99

APIs and other access methods

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

Proprietary protocol
Thrift

C++ API
Java API

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

C#
C++
Java
PHP
Python
Ruby
Scala

C++

C++
Java

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

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

Java

Triggers

yes (cache interceptors and events)

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes (replicated cache)

none

Multi-source replication
Source-replica replication

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

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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

Users and roles with access to stored procedures

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

GridGain Advances Its Unified Real-Time Data Platform to Help Enterprises Accelerate AI-Driven Data Processing
10 July 2024, insideBIGDATA

GridGain Sponsoring Strategic AI and Kafka Conferences This Month
4 September 2024, Datanami

GridGain in-memory data and generative AI
10 May 2024, Blocks & Files

Data Management News for the Week of July 12; Updates from Cloudera, HerculesAI, Oracle & More
12 July 2024, Solutions Review

GridGain Announces Call for Speakers for Virtual Apache Ignite Summit 2024
8 February 2024, Datanami

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

Unveiling Volt Active Data’s game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Announces Key New Hires
26 October 2021, citybiz

Solutions Review Sits Down with VoltDB CEO David Flower
17 April 2018, Solutions Review

VoltDB Aims for Fast Big Data Development
29 January 2015, ADT Magazine

provided by Google News

Share this page