DBMS > 4D vs. GeoMesa vs. SQream DB vs. ToroDB vs. Vitess

System Properties Comparison 4D vs. GeoMesa vs. SQream DB vs. ToroDB vs. Vitess

Editorial information provided by DB-Engines

Name

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

Description

Application development environment with integrated database management system

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

a GPU-based, columnar RDBMS for big data analytics workloads

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	2.58
Rank	#108	Overall
	#54	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Score	0.82
Rank	#209	Overall
	#97	Relational DBMS

Website

www.4d.com

www.geomesa.org

sqream.com

github.com/torodb/server

vitess.io

Technical documentation

developer.4d.com

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

docs.sqream.com

vitess.io/docs

Developer

4D, Inc

CCRi and others

SQream Technologies

8Kdata

The Linux Foundation, PlanetScale

Initial release

1984

2014

2017

2016

2013

Current release

v20, April 2023

4.0.5, February 2024

2022.1.6, December 2022

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

Open Source

AGPL-V3

Open Source

Apache Version 2.0, commercial licenses 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

Scala

C++, CUDA, Haskell, Java, Scala

Java

Server operating systems

OS X
Windows

Linux

All OS with a Java 7 VM

Docker
Linux
macOS

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, ANSI Standard SQL Types

yes

string, integer, double, boolean, date, object_id

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

yes

close to SQL 92

yes

with proprietary extensions

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

.Net
JDBC
ODBC

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

4D proprietary IDE
PHP

C++
Java
JavaScript (Node.js)
Python

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

user defined functions in Python

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

horizontal and vertical partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

depending on storage layer

none

Source-replica replication

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

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

User concepts

Access control

Users and groups

yes

depending on the DBMS used for storage

Access rights for users and roles

Users with fine-grained authorization concept

no user groups or 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

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

SQream Announces Strategic Integration for Powerful Big Data Analytics with Dataiku
9 February 2024, insideBIGDATA

I SQream, you SQream, we all SQream for … data analytics?
5 October 2023, Fierce Network

SQream Technologies raises $39.4 million for GPU-accelerated databases
24 June 2020, VentureBeat

SQream Announces Free Licenses to Organizations Using Data Analytics to Fight the Coronavirus
9 April 2020, Embedded Computing Design

Chinese giant Alibaba leads investment round in Israel big-data startup
30 May 2018, The Times of Israel

provided by Google News

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale grabs YouTube-developed open-source tech, promises Vitess DBaaS with on-the-fly schema changes
18 May 2021, The Register

With Vitess 4.0, database vendor matures cloud-native platform
13 November 2019, TechTarget

Massively Scaling MySQL Using Vitess
19 February 2019, InfoQ.com

They scaled YouTube -- now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

provided by Google News

Share this page