DBMS > BigchainDB vs. Linter vs. Memcached vs. Rockset vs. SQLite

System Properties Comparison BigchainDB vs. Linter vs. Memcached vs. Rockset vs. SQLite

Editorial information provided by DB-Engines

Name

Description

BigchainDB is scalable blockchain database offering decentralization, immutability and native assets

RDBMS for high security requirements

In-memory key-value store, originally intended for caching

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Widely used embeddable, in-process RDBMS

Primary database model

Secondary database models

Spatial DBMS

Relational DBMS
Search engine

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

Score	0.79
Rank	#212	Overall
	#36	Document stores

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	19.42
Rank	#32	Overall
	#4	Key-value stores

Score	0.79
Rank	#211	Overall
	#35	Document stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

Technical documentation

bigchaindb.readthedocs.io/en/latest

github.com/memcached/memcached/wiki

docs.rockset.com

www.sqlite.org/docs.html

Developer

relex.ru

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Rockset

Dwayne Richard Hipp

Initial release

2016

1990

2003

2019

2000

Current release

1.6.25, March 2024

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

Open Source

AGPL v3

commercial

Open Source

BSD license

commercial

Open Source

Public Domain

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

Python

C and C++

C++

Server operating systems

Linux

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

FreeBSD
Linux
OS X
Unix
Windows

hosted

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

Typing

predefined data types such as float or date

yes

dynamic typing

yes

not rigid because of 'dynamic typing' concept.

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.

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

Read-only SQL queries, including JOINs

yes

SQL-92 is not fully supported

APIs and other access methods

CLI Client
RESTful HTTP API

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

Proprietary protocol

HTTP REST

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

Go
Haskell
Java
JavaScript
Python
Ruby

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Go
Java
JavaScript (Node.js)
Python

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Automatic sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

Durability

Support for making data persistent

yes,with MongoDB ord RethinkDB

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

yes

fine grained access rights according to SQL-standard

yes

using SASL (Simple Authentication and Security Layer) protocol

Access rights for users and organizations can be defined via Rockset console

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.