DBMS > LMDB vs. Riak TS vs. SWC-DB vs. Vitess

System Properties Comparison LMDB vs. Riak TS vs. SWC-DB vs. Vitess

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A high performant, light-weight, embedded key-value database library

Riak TS is a distributed NoSQL database optimized for time series data and based on Riak KV

A high performance, scalable Wide Column DBMS

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Time Series DBMS

Document store
Spatial DBMS

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

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

Score	0.28
Rank	#307	Overall
	#27	Time Series DBMS

Score	0.08
Rank	#364	Overall
	#13	Wide column stores

Score	0.88
Rank	#203	Overall
	#95	Relational DBMS

Website

www.symas.com/symas-embedded-database-lmdb

github.com/kashirin-alex/swc-db
www.swcdb.org

vitess.io

Technical documentation

www.lmdb.tech/doc

www.tiot.jp/riak-docs/riak/ts/latest

vitess.io/docs

Developer

Symas

Open Source, formerly Basho Technologies

Alex Kashirin

The Linux Foundation, PlanetScale

Initial release

2011

2015

2020

2013

Current release

0.9.32, January 2024

3.0.0, September 2022

0.5, April 2021

15.0.2, December 2022

License

Commercial or Open Source

Open Source

GPL V3

Open Source

Apache Version 2.0, commercial licenses available

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

Erlang

C++

Server operating systems

Linux
Unix
Windows

Linux
OS X

Linux

Docker
Linux
macOS

Data scheme

schema-free

yes

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.

Secondary indexes

restricted

yes

SQL

Support of SQL

yes, limited

SQL-like query language

yes

with proprietary extensions

APIs and other access methods

HTTP API
Native Erlang Interface

Proprietary protocol
Thrift

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

unofficial client library
C#
C++

unofficial client library
Clojure

unofficial client library
Dart

unofficial client library
Erlang
Go

unofficial client library
Groovy

unofficial client library
Haskell

unofficial client library
Java
JavaScript

unofficial client library
Lisp

unofficial client library
Perl

unofficial client library
PHP
Python
Ruby
Scala

unofficial client library
Smalltalk

unofficial client library

C++

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

Erlang

yes

proprietary syntax

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

links between datasets can be stored

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

Users with fine-grained authorization concept

no user groups or roles

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

Recent citations in the news

Automating SAP S/4HANA Migration with IT-Conductor, BGP Managed Services, and AWS | Amazon Web Services
22 August 2023, AWS Blog

The Tom Brady Data Biography
8 September 2023, StatsBomb

The Lightning Memory-mapped Database
2 March 2016, InfoQ.com

Akamai launches managed database service – Blocks and Files
25 April 2022, Blocks and Files

HarperDB - How and Why We Built It From The Ground Up on NodeJS
28 February 2021, hackernoon.com

provided by Google News

New Basho Data Platform Provides Operational Simplicity for Enterprise Big Data Applications
7 June 2015, insideBIGDATA

Best open source databases for IoT applications
26 May 2017, Open Source For You

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

PlanetScale Serves up Vitess-Powered Serverless MySQL
23 November 2021, The New Stack

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

provided by Google News

Share this page