DBMS > Atos Standard Common Repository vs. Drizzle vs. KeyDB vs. SpaceTime

System Properties Comparison Atos Standard Common Repository vs. Drizzle vs. KeyDB vs. SpaceTime

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

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

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Spatial DBMS

Secondary database models

Relational 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.00
Rank	#385	Overall
	#7	Spatial DBMS

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

github.com/Snapchat/KeyDB
keydb.dev

www.mireo.com/spacetime

Technical documentation

docs.keydb.dev

Developer

Atos Convergence Creators

Drizzle project, originally started by Brian Aker

EQ Alpha Technology Ltd.

Mireo

Initial release

2016

2008

2019

2020

Current release

1703

7.2.4, September 2012

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

BSD-3

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.

Implementation language

Java

C++

Server operating systems

Linux

FreeBSD
Linux
OS X

Linux

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

Typing

predefined data types such as float or date

optional

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.

yes

Secondary indexes

yes

by using the Redis Search module

SQL

Support of SQL

yes

with proprietary extensions

A subset of ANSI SQL is implemented

APIs and other access methods

LDAP

JDBC

Proprietary protocol

RESP - REdis Serialization Protoco

RESTful HTTP API

Supported programming languages

All languages with LDAP bindings

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++
Python

Server-side scripts

Stored procedures

Lua

Triggers

yes

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

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

Atomic execution of specific operations

ACID

Optimistic locking, atomic execution of commands blocks and scripts

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

LDAP bind authentication

Pluggable authentication mechanisms

e.g. LDAP, HTTP

simple password-based access control and ACL

yes

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

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

Share this page