DBMS > AgensGraph vs. GridGain vs. Sadas Engine vs. SiriDB vs. SQLite

System Properties Comparison AgensGraph vs. GridGain vs. Sadas Engine vs. SiriDB vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Multi-model database supporting relational and graph data models and built upon PostgreSQL

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

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

Open Source Time Series DBMS

Widely used embeddable, in-process RDBMS

Primary database model

Graph DBMS
Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	0.23
Rank	#315	Overall
	#26	Graph DBMS
	#140	Relational DBMS

Score	1.55
Rank	#150	Overall
	#26	Key-value stores
	#70	Relational DBMS

Score	0.07
Rank	#373	Overall
	#157	Relational DBMS

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

bitnine.net/agensgraph

Technical documentation

bitnine.net/documentation

www.gridgain.com/docs/index.html

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

docs.siridb.com

www.sqlite.org/docs.html

Developer

Bitnine Global Inc.

GridGain Systems, Inc.

SADAS s.r.l.

Cesbit

Dwayne Richard Hipp

Initial release

2016

2007

2006

2017

2000

Current release

2.1, December 2018

GridGain 8.5.1

8.0

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free trial version available

Open Source

MIT License

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

C++

Server operating systems

Linux
OS X
Windows

Linux
OS X
Solaris
Windows

AIX
Linux
Windows

Linux

server-less

Data scheme

depending on used data model

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numeric data

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

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

yes

SQL-92 is not fully supported

APIs and other access methods

Cypher Query Language
JDBC

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

JDBC
ODBC
Proprietary protocol

HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

C
Java
JavaScript
Python

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
C
C#
C++
Groovy
Java
PHP
Python

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

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

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

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

no, but can be realized using table inheritance

Sharding

horizontal partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

yes (replicated cache)

none

yes

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

managed by 'Learn by Usage'

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

Access rights for users, groups and roles according to SQL-standard

simple rights management via user accounts

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.