DBMS > Databricks vs. EsgynDB vs. Riak KV vs. Yanza

System Properties Comparison Databricks vs. EsgynDB vs. Riak KV vs. Yanza

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Distributed, fault tolerant key-value store

Time Series DBMS for IoT Applications

Primary database model

Document store
Relational DBMS

Relational DBMS

Key-value store

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

Time Series DBMS

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

Score	78.61
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

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

Website

www.databricks.com

www.esgyn.cn

yanza.com

Technical documentation

docs.databricks.com

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

Developer

Databricks

Esgyn

OpenSource, formerly Basho Technologies

Yanza

Initial release

2013

2015

2009

2015

Current release

3.2.0, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache version 2, commercial enterprise edition

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

C++, Java

Erlang

Server operating systems

hosted

Linux

Linux
OS X

Windows

Data scheme

Flexible Schema (defined schema, partial schema, 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

Secondary indexes

yes

restricted

SQL

Support of SQL

with Databricks SQL

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

ADO.NET
JDBC
ODBC

HTTP API
Native Erlang Interface

HTTP API

Supported programming languages

Python
R
Scala

All languages supporting JDBC/ODBC/ADO.Net

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions and aggregates

Java Stored Procedures

Erlang

Triggers

yes

pre-commit hooks and post-commit hooks

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

no "single point of failure"

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication between multi datacenters

selectable replication factor

none

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

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.

User concepts

Access control

fine grained access rights according to SQL-standard

yes, using Riak Security

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.

More resources

DB-Engines blog posts

PostgreSQL is the DBMS of the Year 2023
2 January 2024, Matthias Gelbmann, Paul Andlinger

show all

Recent citations in the news

Databricks expands Seattle presence with office in West 8th
2 May 2024, The Business Journals

Protecting Your AI Investments: Databricks' Breakthrough Security Framework
2 May 2024, Acceleration Economy

Tableau and Databricks Expand Strategic Partnership
2 May 2024, Datanami

Analytics and Data Science News for the Week of May 3; Updates from Databricks, DataRobot, MicroStrategy & More
2 May 2024, Solutions Review

Tableau adds generative AI tools, tightens Databricks bond
30 April 2024, TechTarget

provided by Google News

Basho Revamps Riak Open-Source Database
22 September 2023, InformationWeek

Riak NoSQL Database: Use Cases and Best Practices
23 December 2011, InfoQ.com

Basho, Maker of Riak NoSQL Database, Raises $25M
13 January 2015, Data Center Knowledge

Riak NoSQL snapped up by Bet365
12 September 2017, ComputerWeekly.com

NoSQL pioneer Basho stamps its mark on time stamp data with Riak TS
6 October 2015, The Register

provided by Google News

Share this page