DBMS > Apache Druid vs. GridGain vs. Microsoft SQL Server vs. SiteWhere

System Properties Comparison Apache Druid vs. GridGain vs. Microsoft SQL Server vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open-source analytics data store designed for sub-second OLAP queries on high dimensionality and high cardinality data

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

Microsofts flagship relational DBMS

M2M integration platform for persisting/querying time series data

Primary database model

Relational DBMS
Time Series DBMS

Key-value store
Relational DBMS

Relational DBMS

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	3.34
Rank	#88	Overall
	#48	Relational DBMS
	#7	Time Series DBMS

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

druid.apache.org

www.gridgain.com

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

github.com/sitewhere/sitewhere

Technical documentation

druid.apache.org/docs/latest/design

www.gridgain.com/docs/index.html

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

sitewhere1.sitewhere.io/index.html

Developer

Apache Software Foundation and contributors

GridGain Systems, Inc.

Microsoft

SiteWhere

Initial release

2012

2007

1989

2010

Current release

29.0.1, April 2024

GridGain 8.5.1

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache license v2

commercial

restricted free version is available

Open Source

Common Public Attribution License Version 1.0

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

Java, C++, .Net

C++

Java

Server operating systems

Linux
OS X
Unix

Linux
OS X
Solaris
Windows

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

schema-less columns are supported

yes

predefined scheme

Typing

predefined data types such as float or date

yes

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

SQL for querying

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

yes

APIs and other access methods

JDBC
RESTful HTTP/JSON API

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

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

HTTP REST

Supported programming languages

Clojure
JavaScript
PHP
Python
R
Ruby
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

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

Server-side scripts

Stored procedures

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

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

Triggers

yes (cache interceptors and events)

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

manual/auto, time-based

Sharding

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

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes, via HDFS, S3 or other storage engines

yes (replicated cache)

yes, but depending on the SQL-Server Edition

selectable replication factor

based on HBase

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

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

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

RBAC using LDAP or Druid internals for users and groups for read/write by datasource and system

Security Hooks for custom implementations

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.