DBMS > Memcached vs. Microsoft SQL Server vs. OpenQM vs. OrigoDB vs. TerminusDB

System Properties Comparison Memcached vs. Microsoft SQL Server vs. OpenQM vs. OrigoDB vs. TerminusDB

Editorial information provided by DB-Engines

Name

Description

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

Microsofts flagship relational DBMS

QpenQM is a high-performance, self-tuning, multi-value DBMS

A fully ACID in-memory object graph database

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Key-value store

Relational DBMS

Multivalue DBMS

Document store
Object oriented DBMS

Graph DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
RDF store

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

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	0.17
Rank	#325	Overall
	#29	Graph DBMS

Website

www.memcached.org

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

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

origodb.com

terminusdb.com

Technical documentation

github.com/memcached/memcached/wiki

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

origodb.com/docs

terminusdb.github.io/terminusdb/#

Developer

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Microsoft

Rocket Software, originally Martin Phillips

Robert Friberg et al

DataChemist Ltd.

Initial release

2003

1989

1993

2009

under the name LiveDB

2018

Current release

1.6.25, March 2024

SQL Server 2022, November 2022

3.4-12

11.0.0, January 2023

License

Commercial or Open Source

Open Source

BSD license

commercial

restricted free version is available

Open Source

GPLv2, extended commercial license available

Open Source

GPL V3

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

Prolog, Rust

Server operating systems

FreeBSD
Linux
OS X
Unix
Windows

Linux
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Linux
Windows

Linux

Data scheme

schema-free

yes

with some exceptions

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like query language (WOQL)

APIs and other access methods

Proprietary protocol

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

.NET Client API
HTTP API
LINQ

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

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

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

.Net
Basic
C
Java
Objective C
PHP
Python

.Net

JavaScript
Python

Server-side scripts

Stored procedures

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

yes

Triggers

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

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

yes

horizontal partitioning

client side managed; servers are not synchronized

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

Repcached, a Memcached patch, provides this functionallity

yes, but depending on the SQL-Server Edition

yes

Source-replica replication

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

depending on model

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

yes

in-memory journaling

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

using SASL (Simple Authentication and Security Layer) protocol

fine grained access rights according to SQL-standard

Access rights can be defined down to the item level

Role based authorization

Role-based access control

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.