DBMS > Drizzle vs. KeyDB vs. Linter vs. SiteWhere

System Properties Comparison Drizzle vs. KeyDB vs. Linter vs. SiteWhere

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.

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

RDBMS for high security requirements

M2M integration platform for persisting/querying time series data

Primary database model

Secondary database models

Spatial DBMS

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

Score	0.63
Rank	#232	Overall
	#32	Key-value stores

Score	0.03
Rank	#368	Overall
	#156	Relational DBMS

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Website

github.com/Snapchat/KeyDB
keydb.dev

linter.ru

github.com/sitewhere/sitewhere

Technical documentation

docs.keydb.dev

sitewhere1.sitewhere.io/index.html

Developer

Drizzle project, originally started by Brian Aker

EQ Alpha Technology Ltd.

relex.ru

SiteWhere

Initial release

2008

2019

1990

2010

Current release

7.2.4, September 2012

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

BSD-3

commercial

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

C++

C and C++

Java

Server operating systems

FreeBSD
Linux
OS X

Linux

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

predefined scheme

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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.

Secondary indexes

yes

by using the Redis Search module

yes

SQL

Support of SQL

yes

with proprietary extensions

yes

APIs and other access methods

JDBC

Proprietary protocol

RESP - REdis Serialization Protoco

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

HTTP REST

Supported programming languages

C
C++
Java
PHP

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

Server-side scripts

Stored procedures

Lua

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Source-replica replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

simple password-based access control and ACL

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Snap snaps up database developer KeyDB to make its infrastructure more snappy
12 May 2022, TechCrunch

Introducing Garnet – an open-source, next-generation, faster cache-store for accelerating applications and services
18 March 2024, microsoft.com

Microsoft open-sources unique “Garnet” cache-store; a Redis rival?
19 March 2024, The Stack

Dragonfly 0.13 Database Adds Experimental SSD-Based Data Tiering, More SIMD Work
2 January 2023, Phoronix

Beyond the mainstream database offerings
26 March 2020, TechCentral.ie

provided by Google News

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

Top Open-Source Tools for IoT Development in 2024
5 September 2024, Analytics Insight

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page