DBMS > BoltDB vs. Databricks vs. Drizzle vs. Snowflake

System Properties Comparison BoltDB vs. Databricks vs. Drizzle vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

An embedded key-value store for Go.

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.

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

Primary database model

Key-value store

Document store
Relational DBMS

Relational DBMS

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

Score	0.74
Rank	#220	Overall
	#31	Key-value stores

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

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

github.com/boltdb/bolt

www.databricks.com

www.snowflake.com

Technical documentation

docs.databricks.com

docs.snowflake.net/manuals/index.html

Developer

Databricks

Drizzle project, originally started by Brian Aker

Snowflake Computing Inc.

Initial release

2013

2008

2014

Current release

7.2.4, September 2012

License

Commercial or Open Source

Open Source

MIT License

commercial

Open Source

GNU GPL

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

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

FreeBSD
Linux
OS X

hosted

Data scheme

schema-free

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

yes

with proprietary extensions

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

JDBC

CLI Client
JDBC
ODBC

Supported programming languages

Python
R
Scala

C
C++
Java
PHP

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

user defined functions

Triggers

hooks for callbacks inside the server can be used.

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

Multi-source replication
Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.