DBMS > Citus vs. GridGain vs. SiteWhere vs. SQLite

System Properties Comparison Citus vs. GridGain vs. SiteWhere vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

M2M integration platform for persisting/querying time series data

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store

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

Score	2.13
Rank	#117	Overall
	#56	Relational DBMS

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

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

www.citusdata.com

www.gridgain.com

github.com/sitewhere/sitewhere

www.sqlite.org

Technical documentation

docs.citusdata.com

www.gridgain.com/docs/index.html

sitewhere1.sitewhere.io/index.html

www.sqlite.org/docs.html

Developer

GridGain Systems, Inc.

SiteWhere

Dwayne Richard Hipp

Initial release

2010

2007

2010

2000

Current release

8.1, December 2018

GridGain 8.5.1

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial, open source

Open Source

Common Public Attribution License Version 1.0

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

Java

Server operating systems

Linux

Linux
OS X
Solaris
Windows
z/OS

Linux
OS X
Windows

server-less

Data scheme

yes

predefined scheme

yes

dynamic column types

Typing

predefined data types such as float or date

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

specific XML type available, but no XML query functionality

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

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

yes

SQL-92 is not fully supported

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

C#
C++
Java
PHP
Python
Ruby
Scala

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

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

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

Triggers

yes

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

yes (replicated cache)

selectable replication factor

based on HBase

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

fine grained access rights according to SQL-standard

Role-based access control
Security Hooks for custom implementations

Users with fine-grained authorization concept

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.