DBMS > Databricks vs. GridGain vs. Machbase Neo vs. Snowflake vs. Sphinx

System Properties Comparison Databricks vs. GridGain vs. Machbase Neo vs. Snowflake vs. Sphinx

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.

GridGain is an in-memory computing platform, built on Apache Ignite

TimeSeries DBMS for AIoT and BigData

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

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Document store
Relational DBMS

Columnar
Key-value store
Object oriented DBMS
Relational DBMS

Time Series DBMS

Relational DBMS

Search engine

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

Score	84.24
Rank	#14	Overall
	#2	Document stores
	#9	Relational DBMS

Score	1.48
Rank	#150	Overall
	#1	Columnar
	#26	Key-value stores
	#2	Object oriented DBMS
	#69	Relational DBMS

Score	0.07
Rank	#348	Overall
	#34	Time Series DBMS

Score	133.72
Rank	#7	Overall
	#5	Relational DBMS

Score	5.97
Rank	#56	Overall
	#5	Search engines

Website

Technical documentation

docs.databricks.com

www.gridgain.com/docs/index.html

machbase.com/dbms

docs.snowflake.net/manuals/index.html

sphinxsearch.com/docs

Developer

Databricks

GridGain Systems, Inc.

Machbase

Snowflake Computing Inc.

Sphinx Technologies Inc.

Initial release

2013

2007

2013

2014

2001

Current release

GridGain 8.5.1

V8.0, August 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

commercial, open source

commercial

free test version available

commercial

Open Source

GPL version 2, commercial licence available

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++, .Net, Python, REST, SQL

C++

Server operating systems

hosted

Linux
OS X
Solaris
Windows
z/OS

Linux
macOS
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

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

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

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

full-text index on all search fields

SQL

Support of SQL

with Databricks SQL

ANSI-99 for query and DML statements, subset of DDL

SQL-like query language

yes

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

CLI Client
JDBC
ODBC

Proprietary protocol

Supported programming languages

Python
R
Scala

C#
C++
Java
PHP
Python
Ruby
Scala

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions and aggregates

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes (replicated cache)

selectable replication factor

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes (compute grid and hadoop accelerator)

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

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

The original contents of fields are not stored in the Sphinx index.

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

volatile and lookup table

User concepts

Access control

Role-based access control
Security Hooks for custom implementations

simple password-based access control

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.