DBMS > 4D vs. EventStoreDB vs. GridGain vs. RRDtool vs. SQLite

System Properties Comparison 4D vs. EventStoreDB vs. GridGain vs. RRDtool vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Industrial-strength, open-source database solution built from the ground up for event sourcing.

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

Industry standard data logging and graphing tool for time series data. RRD is an acronym for round-robin database.

The data is stored in a circular buffer, thus the system storage footprint remains constant over time.

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Event Store

Key-value store
Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	1.10
Rank	#179	Overall
	#1	Event Stores

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

Score	1.87
Rank	#136	Overall
	#11	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

www.4d.com

www.eventstore.com

www.gridgain.com

oss.oetiker.ch/rrdtool

www.sqlite.org

Technical documentation

developer.4d.com

developers.eventstore.com

www.gridgain.com/docs/index.html

oss.oetiker.ch/rrdtool/doc

www.sqlite.org/docs.html

Developer

4D, Inc

Event Store Limited

GridGain Systems, Inc.

Tobias Oetiker

Dwayne Richard Hipp

Initial release

1984

2012

2007

1999

2000

Current release

v20, April 2023

21.2, February 2021

GridGain 8.5.1

1.8.0, 2022

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

commercial

Open Source

GPL V2 and FLOSS

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

Implementations in Java (e.g. RRD4J) and C# available

Server operating systems

OS X
Windows

Linux
Windows

Linux
OS X
Solaris
Windows

HP-UX
Linux

server-less

Data scheme

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Numeric data only

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

Exporting into and restoring from XML files possible

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

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

yes

SQL-92 is not fully supported

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

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

in-process shared library
Pipes

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

4D proprietary IDE
PHP

C#
C++
Java
PHP
Python
Ruby
Scala

with librrd library
C#

with a different implementation of RRDTool
Java

with a different implementation of RRDTool
JavaScript (Node.js)

with a different implementation of RRDTool
Lua
Perl
PHP

with a wrapper library
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

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

none

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

yes (replicated cache)

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

none

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

by using the rrdcached daemon

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

Users and groups

Security Hooks for custom implementations

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.