DBMS > BigObject vs. PostGIS vs. RavenDB vs. Splice Machine

System Properties Comparison BigObject vs. PostGIS vs. RavenDB vs. Splice Machine

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Spatial extension of PostgreSQL

Open Source Operational and Transactional Enterprise NoSQL Document Database

Open-Source SQL RDBMS for Operational and Analytical use cases with native Machine Learning, powered by Hadoop and Spark

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Spatial DBMS

Document store

Relational DBMS

Secondary database models

Relational DBMS

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Website

Technical documentation

docs.bigobject.io

postgis.net/documentation

ravendb.net/docs

splicemachine.com/how-it-works

Developer

BigObject, Inc.

Hibernating Rhinos

Splice Machine

Initial release

2015

2005

2010

2014

Current release

3.4.2, February 2024

5.4, July 2022

3.1, March 2021

License

Commercial or Open Source

commercial

free community edition available

Open Source

GPL v2.0

Open Source

AGPL version 3, commercial license available

Open Source

AGPL 3.0, commercial license available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux
macOS
Raspberry Pi
Windows

Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

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

SQL

Support of SQL

SQL-like DML and DDL statements

yes

SQL-like query language (RQL)

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

JDBC
Native Spark Datasource
ODBC

Supported programming languages

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C#
C++
Java
JavaScript (Node.js)
Python
R
Scala

Server-side scripts

Stored procedures

Lua

user defined functions

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

based on PostgreSQL

Sharding

Shared Nothhing Auto-Sharding, Columnar Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

none

yes

based on PostgreSQL

Multi-source replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Yes, via Full Spark Integration

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

ACID, Cluster-wide transaction available

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

yes, multi-version concurrency control (MVCC)

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

yes

based on PostgreSQL

Authorization levels configured per client per database

Access rights for users, groups and roles according to SQL-standard

More information provided by the system vendor

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

RavenDB Launches Version 6.0 Lightning Fast Queries, Data Integrations, Corax Indexing Engine, and Sharding
3 October 2023, PR Newswire

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

RavenDB Adds Graph Queries
15 May 2019, Datanami

provided by Google News

Machine learning data pipeline outfit Splice Machine files for insolvency
26 August 2021, The Register

Splice Machine Launches the Splice Machine Feature Store to Simplify Feature Engineering and Democratize Machine ...
19 January 2021, PR Newswire

Splice Machine Launches Feature Store to Simplify Feature Engineering
19 January 2021, Datanami

Distributed SQL System Review: Snowflake vs Splice Machine
18 September 2019, Towards Data Science

Splice Machine splices into AWS
8 February 2017, SDTimes.com

provided by Google News

Share this page