DBMS > 4D vs. Riak KV vs. SAP HANA vs. Snowflake

System Properties Comparison 4D vs. Riak KV vs. SAP HANA vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Application development environment with integrated database management system

Distributed, fault tolerant key-value store

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

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Key-value store

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

Relational DBMS

Secondary database models

Document store
Graph DBMS

with SAP Hana, Enterprise Edition
Spatial DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	4.10
Rank	#82	Overall
	#9	Key-value stores

Score	44.69
Rank	#22	Overall
	#16	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.4d.com

www.sap.com/products/hana.html

www.snowflake.com

Technical documentation

developer.4d.com

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

help.sap.com/hana

docs.snowflake.net/manuals/index.html

Developer

4D, Inc

OpenSource, formerly Basho Technologies

SAP

Snowflake Computing Inc.

Initial release

1984

2009

2010

2014

Current release

v20, April 2023

3.2.0, December 2022

2.0 SPS07 (April 4, 2023), April 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

commercial

Cloud-based only

Only available as a cloud service

also available as a cloud based service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Erlang

Server operating systems

OS X
Windows

Linux
OS X

Appliance or cloud-service

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Secondary indexes

yes

restricted

yes

SQL

Support of SQL

yes

close to SQL 92

yes

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

HTTP API
Native Erlang Interface

JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

4D proprietary IDE
PHP

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

Erlang

SQLScript, R

user defined functions

Triggers

yes

pre-commit hooks and post-commit hooks

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

no "single point of failure"

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

yes

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

Foreign keys

Referential integrity

yes

links between data sets can be stored

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

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 and groups

yes, using Riak Security

yes

Users with fine-grained authorization concept, user roles and pluggable authentication

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.