DBMS > Drizzle vs. IBM Cloudant vs. Kinetica vs. Microsoft SQL Server vs. SiteWhere

System Properties Comparison Drizzle vs. IBM Cloudant vs. Kinetica vs. Microsoft SQL Server vs. SiteWhere

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Database as a Service offering based on Apache CouchDB

Fully vectorized database across both GPUs and CPUs

Microsofts flagship relational DBMS

M2M integration platform for persisting/querying time series data

Primary database model

Secondary database models

Spatial DBMS
Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

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

Score	2.68
Rank	#106	Overall
	#20	Document stores

Score	0.64
Rank	#236	Overall
	#109	Relational DBMS

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Website

www.ibm.com/products/cloudant

www.kinetica.com

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

github.com/sitewhere/sitewhere

Technical documentation

cloud.ibm.com/docs/Cloudant

docs.kinetica.com

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

sitewhere1.sitewhere.io/index.html

Developer

Drizzle project, originally started by Brian Aker

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Kinetica

Microsoft

SiteWhere

Initial release

2008

2010

2012

1989

2010

Current release

7.2.4, September 2012

7.1, August 2021

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

GNU GPL

commercial

restricted free version is available

Open Source

Common Public Attribution License Version 1.0

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

C++

Erlang

C, C++

C++

Java

Server operating systems

FreeBSD
Linux
OS X

hosted

Linux

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

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

yes

with proprietary extensions

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC

RESTful HTTP/JSON API

JDBC
ODBC
RESTful HTTP API

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

HTTP REST

Supported programming languages

C
C++
Java
PHP

C#
Java
JavaScript
Objective-C
PHP
Ruby

C++
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

user defined functions

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

Triggers

hooks for callbacks inside the server can be used.

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Partitioning methods

Methods for storing different data on different nodes

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

Multi-source replication
Source-replica replication

Source-replica replication

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

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

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

GPU vRAM or System RAM

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users can be defined per database

Access rights for users and roles on table level

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.