DBMS > GeoMesa vs. Sadas Engine vs. Splice Machine vs. ToroDB vs. VictoriaMetrics

System Properties Comparison GeoMesa vs. Sadas Engine vs. Splice Machine vs. ToroDB vs. VictoriaMetrics

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

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

A MongoDB-compatible JSON document store, built on top of PostgreSQL

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.00
Rank	#383	Overall
	#158	Relational DBMS

Score	0.54
Rank	#250	Overall
	#114	Relational DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

www.geomesa.org

www.sadasengine.com

splicemachine.com

github.com/torodb/server

victoriametrics.com

Technical documentation

www.geomesa.org/documentation/stable/user/index.html

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

splicemachine.com/how-it-works

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

CCRi and others

SADAS s.r.l.

Splice Machine

8Kdata

VictoriaMetrics

Initial release

2014

2006

2014

2016

2018

Current release

4.0.5, February 2024

8.0

3.1, March 2021

v1.91, May 2023

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free trial version available

Open Source

AGPL 3.0, commercial license available

Open Source

AGPL-V3

Open Source

Apache Version 2.0

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

Scala

C++

Java

Server operating systems

AIX
Linux
Windows

Linux
OS X
Solaris
Windows

All OS with a Java 7 VM

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol

JDBC
Native Spark Datasource
ODBC

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

.Net
C
C#
C++
Groovy
Java
PHP
Python

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

Server-side scripts

Stored procedures

yes

Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

horizontal partitioning

Shared Nothhing Auto-Sharding, Columnar Partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

none

Multi-source replication
Source-replica replication

Source-replica replication

Synchronous 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

depending on storage layer

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual 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

yes, multi-version concurrency control (MVCC)

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.

depending on storage layer

yes

managed by 'Learn by Usage'

yes

User concepts

Access control

yes

depending on the DBMS used for storage

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

Access rights for users and roles

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

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

How Splice Machine's Data Platform for Intelligent Apps Works
29 September 2020, eWeek

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

provided by Google News

OpenTelemetry Is Too Complicated, VictoriaMetrics Says
1 April 2024, Datanami

KubeCon24: VictoriaMetrics' Simpler Alternative to Prometheus
20 March 2024, The New Stack

Green coding - VictoriaMetrics: The efficiency vs complexity trade-off
15 May 2024, ComputerWeekly.com

How VictoriaMetrics' open source approach led to mass industry adoption
3 May 2024, Tech.eu

VictoriaMetrics Machine Learning takes monitoring to the next level
19 March 2024, businesswire.com

provided by Google News

Share this page