DBMS > Databricks vs. Geode vs. Google BigQuery vs. Percona Server for MongoDB

System Properties Comparison Databricks vs. Geode vs. Google BigQuery vs. Percona Server for MongoDB

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

Large scale data warehouse service with append-only tables

A drop-in replacement for MongoDB Community Edition with enterprise-grade features.

Primary database model

Document store
Relational DBMS

Key-value store

Relational DBMS

Document store

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	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.52
Rank	#254	Overall
	#39	Document stores

Website

www.databricks.com

geode.apache.org

cloud.google.com/bigquery

www.percona.com/mongodb/software/percona-server-for-mongodb

Technical documentation

docs.databricks.com

geode.apache.org/docs

cloud.google.com/bigquery/docs

docs.percona.com/percona-distribution-for-mongodb

Developer

Databricks

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

Google

Percona

Initial release

2013

2002

2010

2015

Current release

1.1, February 2017

3.4.10-2.10, November 2017

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

commercial

Open Source

GPL Version 2

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

C++

Server operating systems

hosted

All OS with a Java VM

the JDK (8 or later) is also required

hosted

Linux

Data scheme

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

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

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

RESTful HTTP/JSON API

proprietary protocol using JSON

Supported programming languages

Python
R
Scala

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

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

Actionscript
C
C#
C++
Clojure
ColdFusion
D
Dart
Delphi
Erlang
Go
Groovy
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Perl
PHP
PowerShell
Prolog
Python
R
Ruby
Scala
Smalltalk

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

in JavaScript

JavaScript

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

Source-replica replication

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

ACID

yes, on a single node

Since BigQuery is designed for querying data

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

via In-Memory Engine

User concepts

Access control

Access rights per client and object definable

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Access rights for users and roles

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.