DBMS > FatDB vs. Geode vs. Microsoft Azure Data Explorer vs. SQLite

System Properties Comparison FatDB vs. Geode vs. Microsoft Azure Data Explorer vs. SQLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Fully managed big data interactive analytics platform

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

column oriented

Relational DBMS

Secondary database models

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.51
Rank	#147	Overall
	#25	Key-value stores

Score	3.28
Rank	#83	Overall
	#45	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

geode.apache.org

azure.microsoft.com/services/data-explorer

www.sqlite.org

Technical documentation

geode.apache.org/docs

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

www.sqlite.org/docs.html

Developer

FatCloud

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Microsoft

Dwayne Richard Hipp

Initial release

2012

2002

2019

2000

Current release

1.1, February 2017

cloud service with continuous releases

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

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

Server operating systems

Windows

All OS with a Java VM

the JDK (8 or later) is also required

hosted

server-less

Data scheme

schema-free

Fixed schema with schema-less datatypes (dynamic)

yes

dynamic column types

Typing

predefined data types such as float or date

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

Via inetgration in SQL Server

SQL-like query language (OQL)

Kusto Query Language (KQL), SQL subset

yes

SQL-92 is not fully supported

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Java Client API
Memcached protocol
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

.Net
All JVM based languages
C++
Groovy
Java
Scala

.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

via applications

user defined functions

Yes, possible languages: KQL, Python, R

Triggers

yes

via applications

yes

Cache Event Listeners

yes

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

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source 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

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

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

Can implement custom security layer via applications

Access rights per client and object definable

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.