DBMS > Datastax Enterprise vs. EDB Postgres vs. Riak KV

System Properties Comparison Datastax Enterprise vs. EDB Postgres vs. Riak KV

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

DataStax Enterprise (DSE) is the always-on, scalable data platform built on Apache Cassandra and designed for hybrid Cloud. DSE integrates graph, search, analytics, administration, developer tooling, and monitoring into a unified platform.

The EDB Postgres Platform is an enterprise-class data management platform based on the open source database PostgreSQL with flexible deployment options and Oracle compatibility features, complemented by tool kits for management, integration, and migration.

Distributed, fault tolerant key-value store

Primary database model

Wide column store

Relational DBMS

Key-value store

with links between data sets and object tags for the creation of secondary indexes

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Search engine
Vector DBMS

Document store
Spatial DBMS

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

Score	3.89
Rank	#69	Overall
	#4	Wide column stores

Score	1.66
Rank	#131	Overall
	#61	Relational DBMS

Score	3.39
Rank	#77	Overall
	#9	Key-value stores

Website

www.datastax.com/products/datastax-enterprise

www.enterprisedb.com

Technical documentation

docs.datastax.com

www.enterprisedb.com/docs

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

Developer

DataStax

EnterpriseDB

OpenSource, formerly Basho Technologies

Initial release

2011

2005

2009

Current release

6.8, April 2020

14, December 2021

3.2.0, December 2022

License

Commercial or Open Source

commercial

BSD for PostgreSQL-components

Open Source

Apache version 2, commercial enterprise edition

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

Erlang

Server operating systems

Linux
OS X

Linux
Windows

Linux
OS X

Data scheme

schema-free

yes

schema-free

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.

yes

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

restricted

SQL

Support of SQL

SQL-like DML and DDL statements (CQL); Spark SQL

yes

standard with numerous extensions

APIs and other access methods

Proprietary protocol

CQL (Cassandra Query Language)
TinkerPop Gremlin

with DSE Graph

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP API
Native Erlang Interface

Supported programming languages

C
C#
C++
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C++
Delphi
Java
Perl
PHP
Python
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

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

horizontal partitioning

by hash, list or range

Sharding

no "single point of failure"

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware, advanced replication for edge computing

Multi-source replication

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency
Tunable Consistency

consistency level can be individually decided with each write operation

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

links between data sets can be stored

Transaction concepts

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

Atomicity and isolation are supported for single operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

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

Access rights for users can be defined per object

fine grained access rights according to SQL-standard

yes, using Riak Security

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.

Share this page