DBMS > Faircom EDGE vs. GridGain vs. Microsoft Azure Data Explorer vs. Microsoft SQL Server vs. XTDB

System Properties Comparison Faircom EDGE vs. GridGain vs. Microsoft Azure Data Explorer vs. Microsoft SQL Server vs. XTDB

Editorial information provided by DB-Engines

Name

Description

FairCom EDGE is an Industry 4.0 solution built to integrate, collect, aggregate and synchronize mission-critical data in edge computing environments

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

Fully managed big data interactive analytics platform

Microsofts flagship relational DBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Key-value store
Relational DBMS

Relational DBMS

column oriented

Relational DBMS

Document store

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

Document store
Graph DBMS
Spatial DBMS

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

Score	0.09
Rank	#362	Overall
	#53	Key-value stores
	#155	Relational DBMS

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

Score	3.80
Rank	#81	Overall
	#43	Relational DBMS

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

www.faircom.com/products/faircom-edge

www.gridgain.com

azure.microsoft.com/services/data-explorer

www.microsoft.com/en-us/sql-server

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

docs.faircom.com/docs/en/UUID-23d4f1fd-d213-f6d5-b92e-9b7475baa14e.html

www.gridgain.com/docs/index.html

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

learn.microsoft.com/en-US/sql/sql-server

www.xtdb.com/docs

Developer

FairCom Corporation

GridGain Systems, Inc.

Microsoft

Juxt Ltd.

Initial release

1979

2007

2019

1989

2019

Current release

V3, October 2020

GridGain 8.5.1

cloud service with continuous releases

SQL Server 2022, November 2022

1.19, September 2021

License

Commercial or Open Source

commercial

Restricted, free version available

commercial

restricted free version is available

Open Source

MIT License

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.

SQLServer Flex @ STACKIT offers a managed version of SQL Server with adjustable CPU, RAM, storage amount and speed, in enterprise grade to perfectly match all application requirements. All services are 100% GDPR-compliant.

Implementation language

ANSI C, C++

Java, C++, .Net

C++

Clojure

Server operating systems

Android
Linux

ARM, x86
Raspbian
Windows

Linux
OS X
Solaris
Windows

hosted

Linux
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

yes

Fixed schema with schema-less datatypes (dynamic)

yes

schema-free

Typing

predefined data types such as float or date

yes, ANSI Standard SQL Types

yes

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

yes

yes, extensible-data-notation format

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

yes

ANSI SQL queries

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

Kusto Query Language (KQL), SQL subset

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

ADO.NET
Direct SQL
IoT Microservice layer
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC
RESTful HTTP API

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

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

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

HTTP REST
JDBC

Supported programming languages

C
C#
C++
Java
JavaScript
PHP
Python
VB.Net

C#
C++
Java
PHP
Python
Ruby
Scala

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Clojure
Java

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

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

Yes, possible languages: KQL, Python, R

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

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

File partitioning

Customizable business rules for partitioning

Sharding

Implicit feature of the cloud service

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous and asynchronous realtime replication based on transaction logs

yes (replicated cache)

yes

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

yes, but depending on the SQL-Server Edition

yes, each node contains all data

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

when using SQL

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

across SQL and NoSQL

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

yes

User concepts

Access control

Fine grained user, group and file access rights managed across SQL (per ANSI standard) and NoSQL.

Security Hooks for custom implementations

Azure Active Directory Authentication

fine grained access rights according to SQL-standard

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.