DBMS > Databricks vs. GeoSpock vs. LokiJS vs. Snowflake

System Properties Comparison Databricks vs. GeoSpock vs. LokiJS vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be 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.

Spatial and temporal data processing engine for extreme data scale

In-memory JavaScript DBMS

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

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store

Relational DBMS

Secondary database models

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.43
Rank	#264	Overall
	#42	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.databricks.com

geospock.com

github.com/techfort/LokiJS

www.snowflake.com

Technical documentation

docs.databricks.com

techfort.github.io/LokiJS

docs.snowflake.net/manuals/index.html

Developer

Databricks

GeoSpock

Snowflake Computing Inc.

Initial release

2013

2014

Current release

2.0, September 2019

License

Commercial or Open Source

commercial

Open Source

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, Javascript

JavaScript

Server operating systems

hosted

server-less, requires a JavaScript environment (browser, Node.js)

hosted

Data scheme

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

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

temporal, categorical

yes

via views

SQL

Support of SQL

with Databricks SQL

ANSI SQL for query only (using Presto)

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

JavaScript API

CLI Client
JDBC
ODBC

Supported programming languages

Python
R
Scala

JavaScript

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

atomic operations within a single collection possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Serialization of a DB in a Node.JS/Cordova/PhoneGap environment. Usage of the IndexedDB-API in a browser.

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 table

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.