DBMS > Databricks vs. Geode vs. SAP SQL Anywhere vs. Snowflake

System Properties Comparison Databricks vs. Geode vs. SAP SQL Anywhere vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

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

Primary database model

Document store
Relational DBMS

Key-value store

Relational 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	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.databricks.com

geode.apache.org

www.sap.com/products/technology-platform/sql-anywhere.html

www.snowflake.com

Technical documentation

docs.databricks.com

geode.apache.org/docs

help.sap.com/docs/SAP_SQL_Anywhere

docs.snowflake.net/manuals/index.html

Developer

Databricks

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

SAP

formerly Sybase

Snowflake Computing Inc.

Initial release

2013

2002

1992

2014

Current release

1.1, February 2017

17, July 2015

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

AIX
HP-UX
Linux
OS X
Solaris
Windows

hosted

Data scheme

Flexible Schema (defined schema, partial schema, schema free)

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

SQL

Support of SQL

with Databricks SQL

SQL-like query language (OQL)

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Java Client API
Memcached protocol
RESTful HTTP API

ADO.NET
HTTP API
JDBC
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

Python
R
Scala

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

yes, in C/C++, Java, .Net or Perl

user defined functions

Triggers

yes

Cache Event Listeners

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Source-replica replication

Database mirroring

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes, on a single node

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

Access rights per client and object definable

fine grained access rights according to SQL-standard

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

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.