DBMS > Kinetica vs. Memcached vs. OrigoDB vs. Rockset vs. SAP HANA

System Properties Comparison Kinetica vs. Memcached vs. OrigoDB vs. Rockset vs. SAP HANA

Editorial information provided by DB-Engines

Name

Description

Fully vectorized database across both GPUs and CPUs

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

A fully ACID in-memory object graph database

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

In-memory, column based data store. Available as appliance or cloud service

Primary database model

Relational DBMS

Key-value store

Document store
Object oriented DBMS

Document store

Relational DBMS

Secondary database models

Spatial DBMS
Time Series DBMS

Relational DBMS
Search engine

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	0.66
Rank	#234	Overall
	#107	Relational DBMS

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

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#18	Object oriented DBMS

Score	0.82
Rank	#212	Overall
	#36	Document stores

Score	44.27
Rank	#23	Overall
	#16	Relational DBMS

Website

www.sap.com/products/hana.html

Technical documentation

docs.kinetica.com

github.com/memcached/memcached/wiki

origodb.com/docs

docs.rockset.com

help.sap.com/hana

Developer

Kinetica

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Robert Friberg et al

Rockset

SAP

Initial release

2012

2003

2009

under the name LiveDB

2019

2010

Current release

7.1, August 2021

1.6.27, May 2024

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

BSD license

Open Source

commercial

Cloud-based only

Only available as a cloud service

yes

also available as a cloud based service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C, C++

C++

Server operating systems

Linux

FreeBSD
Linux
OS X
Unix
Windows

Linux
Windows

hosted

Appliance or cloud-service

Data scheme

yes

schema-free

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

dynamic typing

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.

can be achieved using .NET

ingestion from XML files supported

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like DML and DDL statements

Read-only SQL queries, including JOINs

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Proprietary protocol

.NET Client API
HTTP API
LINQ

HTTP REST

JDBC
ODBC

Supported programming languages

C++
Java
JavaScript (Node.js)
Python

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

.Net

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

yes

SQLScript, R

Triggers

yes

triggers when inserted values for one or more columns fall within a specified range

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

Automatic sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Repcached, a Memcached patch, provides this functionallity

Source-replica replication

yes

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

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 capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

GPU vRAM or System RAM

yes

User concepts

Access control

Access rights for users and roles on table level

yes

using SASL (Simple Authentication and Security Layer) protocol

Role based authorization

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

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.