DBMS > AntDB vs. GeoMesa vs. ToroDB

System Properties Comparison AntDB vs. GeoMesa vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

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

Description

A scalable, multi-tenant, MPP-architectured RDBMS for OLTP and OLAP operations, highly compatible with Oracle

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

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

Primary database model

Relational DBMS

Spatial DBMS

Document store

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

Score	0.23
Rank	#317	Overall
	#141	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Website

www.asiainfo.com/en_us/product_aisware_antdb_detail.html

www.geomesa.org

github.com/torodb/server

Technical documentation

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

Developer

AsiaInfo Technologies Limited

CCRi and others

8Kdata

Initial release

2014

2016

Current release

5.0.0, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

AGPL-V3

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

Java

Server operating systems

All OS with a Java 7 VM

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

SQL2016 compliant

APIs and other access methods

JDBC
MySQL protocol compliant
ODBC

Server-side scripts

Stored procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

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

Eventual Consistency
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

In-memory capabilities

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

yes

depending on storage layer

User concepts

Access control

yes

depending on the DBMS used for storage

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

AntDB: Answer to Database Evolution - Hyperconverged All-in-One Streaming Engine
22 June 2023, Bei Mo, AntDB (sponsor)

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Share this page