DBMS > Datomic vs. GridGain vs. Informix vs. Microsoft Azure Data Explorer vs. SQLite

System Properties Comparison Datomic vs. GridGain vs. Informix vs. Microsoft Azure Data Explorer vs. SQLite

Editorial information provided by DB-Engines

Name

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

A secure embeddable database from IBM, positioned besides IBM Db2 as a relatively low-cost product optimized for OLTP and Internet of Things data

Fully managed big data interactive analytics platform

Widely used embeddable, in-process RDBMS

Primary database model

Relational DBMS

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Relational DBMS

Since Version 12.10 support for JSON/BSON datatypes compatible with MongoDB

Relational DBMS

column oriented

Relational DBMS

Secondary database models

Document store
Spatial DBMS
Time Series DBMS

with Informix TimeSeries Extension

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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

Score	1.55
Rank	#144	Overall
	#67	Relational DBMS

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

Score	16.32
Rank	#35	Overall
	#21	Relational DBMS

Score	3.28
Rank	#83	Overall
	#45	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

www.datomic.com

www.gridgain.com

www.ibm.com/products/informix

azure.microsoft.com/services/data-explorer

www.sqlite.org

Technical documentation

docs.datomic.com

www.gridgain.com/docs/index.html

informix.hcldoc.com
www.ibm.com/support/knowledgecenter/SSGU8G/welcomeIfxServers.html

docs.microsoft.com/en-us/azure/data-explorer

www.sqlite.org/docs.html

Developer

Cognitect

GridGain Systems, Inc.

IBM, HCL Technologies

Effective May 1st, 2017, HCL took on development, technical support, and product management teams, and works jointly with IBM on product strategy, marketing, and sales.

Microsoft

Dwayne Richard Hipp

Initial release

2012

2007

1984

2019

2000

Current release

1.0.7180, July 2024

GridGain 8.5.1

14.10.FC5, November 2020

cloud service with continuous releases

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

limited edition free

commercial, open source

commercial

free developer edition available

commercial

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java, Clojure

Java, C++, .Net, Python, REST, SQL

C, C++ and Java

Server operating systems

All OS with a Java VM

Linux
OS X
Solaris
Windows
z/OS

AIX
HP-UX
Linux
macOS
Solaris
Windows

hosted

server-less

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

yes

dynamic column types

Typing

predefined data types such as float or date

yes

Since Version 12.10 support for JSON/BSON datatypes

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

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

all fields are automatically indexed

yes

SQL

Support of SQL

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

yes

Kusto Query Language (KQL), SQL subset

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP API

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

JDBC
JSON API

MongoDB compatible
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Clojure
Java

C#
C++
Java
PHP
Python
Ruby
Scala

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

.Net
Go
Java
JavaScript (Node.js)
PowerShell
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

Transaction Functions

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

yes

Yes, possible languages: KQL, Python, R

Triggers

By using transaction functions

yes (cache interceptors and events)

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

yes (replicated cache)

Multi-source replication
Source-replica replication

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

recommended only for testing and development

yes

User concepts

Access control

Role-based access control
Security Hooks for custom implementations

Users with fine-grained authentication, authorization, and auditing controls

Azure Active Directory Authentication

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.