DBMS > Drizzle vs. etcd vs. Microsoft SQL Server vs. Oracle Coherence

System Properties Comparison Drizzle vs. etcd vs. Microsoft SQL Server vs. Oracle Coherence

Please select another system to include it in the comparison.

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.

A distributed reliable key-value store

Microsofts flagship relational DBMS

Oracles in-memory data grid solution

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	7.03
Rank	#54	Overall
	#5	Key-value stores

Score	821.56
Rank	#3	Overall
	#3	Relational DBMS

Score	1.97
Rank	#129	Overall
	#22	Key-value stores

Website

etcd.io
github.com/etcd-io/etcd

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

www.oracle.com/java/coherence

Technical documentation

etcd.io/docs
github.com/etcd-io/etcd/tree/master/Documentation

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

docs.oracle.com/en/middleware/standalone/coherence

Developer

Drizzle project, originally started by Brian Aker

Microsoft

Oracle

Initial release

2008

1989

2007

Current release

7.2.4, September 2012

3.4, August 2019

SQL Server 2022, November 2022

14.1, August 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache Version 2.0

commercial

restricted free version is available

commercial

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.

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

C++

Java

Server operating systems

FreeBSD
Linux
OS X

FreeBSD
Linux
Windows

experimental

Linux
Windows

All OS with a Java VM

Data scheme

yes

schema-free

yes

schema-free

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

yes

APIs and other access methods

JDBC

gRPC
JSON over HTTP

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

JCache
JPA
RESTful HTTP API

Supported programming languages

C
C++
Java
PHP

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript (Node.js)
Perl
PHP
Python
R
Ruby
Rust
Scala
Tcl

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

.Net
C++
Java

Server-side scripts

Stored procedures

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

Triggers

hooks for callbacks inside the server can be used.

yes, watching key changes

yes

Live Events

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Using Raft consensus algorithm to ensure data replication with strong consistency among multiple replicas.

yes, but depending on the SQL-Server Edition

yes, with selectable consistency level

MapReduce

Offers an API for user-defined Map/Reduce methods

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

configurable

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

optionally

In-memory capabilities

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

yes

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

authentification to access the cache via certificates or http basic 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.