DBMS > GridDB vs. IRONdb vs. MarkLogic vs. SQLite

System Properties Comparison GridDB vs. IRONdb vs. MarkLogic vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Scalable in-memory time series database optimized for IoT and Big Data

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Operational and transactional Enterprise NoSQL database

Widely used embeddable, in-process RDBMS

Primary database model

Time Series DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Relational DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	2.09
Rank	#120	Overall
	#10	Time Series DBMS

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Website

griddb.net

www.circonus.com/solutions/time-series-database/

www.marklogic.com

www.sqlite.org

Technical documentation

docs.griddb.net

docs.circonus.com/irondb/category/getting-started

docs.marklogic.com

www.sqlite.org/docs.html

Developer

Toshiba Corporation

Circonus LLC.

MarkLogic Corp.

Dwayne Richard Hipp

Initial release

2013

2017

2001

2000

Current release

5.1, August 2022

V0.10.20, January 2018

11.0, December 2022

3.46.0 (23 May 2024), May 2024

License

Commercial or Open Source

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

restricted free version is available

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

C++

C and C++

C++

Server operating systems

Linux

Linux
OS X
Windows

server-less

Data scheme

yes

schema-free

Schema can be enforced

yes

dynamic column types

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

yes

text, numeric, histograms

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

SQL92, SQL-like TQL (Toshiba Query Language)

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

SQL92

yes

SQL-92 is not fully supported

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

HTTP API

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

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

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
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, in Lua

yes

via XQuery or JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Automatic, metric affinity per node

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

configurable replication factor, datacenter aware

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate consistency within container, eventual consistency across containers

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID at container level

ACID

can act as a resource manager in an XA/JTA transaction

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

yes, with Range Indexes

yes

User concepts

Access control

Access rights for users can be defined per database

Role-based access control at the document and subdocument levels

More information provided by the system vendor

Specific characteristics

GridDB is a highly scalable, in-memory time series database optimized for IoT and...
» more

Competitive advantages

1. Optimized for IoT Equipped with Toshiba's proprietary key-container data model...
» more

Typical application scenarios

Factory IoT, Automative Industry, Energy, BEMS, Smart Community, Monitoring system.
» more

Key customers

Denso International [see use case ] An Electric Power company [see use case ] Ishinomaki...
» more

Market metrics

GitHub trending repository
» more

Licensing and pricing models

Open Source license (AGPL v3 & Apache v2) Commercial license (subscription)
» more

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.