DBMS > Datomic vs. GeoMesa vs. SAP Advantage Database Server vs. TimescaleDB

System Properties Comparison Datomic vs. GeoMesa vs. SAP Advantage Database Server vs. TimescaleDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Low-cost RDBMS with access to ISAM and FoxPro data structures

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

Primary database model

Secondary database models

Relational DBMS

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

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Website

www.datomic.com

www.geomesa.org

www.sap.com/products/advantage-database-server.html

www.timescale.com

Technical documentation

docs.datomic.com

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

docs.timescale.com

Developer

Cognitect

CCRi and others

Sybase, SAP

Timescale

Initial release

2012

2014

1993

2017

Current release

1.0.7075, December 2023

5.0.0, May 2024

2.15.0, May 2024

License

Commercial or Open Source

commercial

limited edition free

Open Source

Apache License 2.0

commercial

Open Source

Apache 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

Java, Clojure

Scala

Server operating systems

All OS with a Java VM

Linux
Windows

Linux
OS X
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

Supported programming languages

Clojure
Java

Delphi
Perl
PHP

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

Transaction Functions

yes

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

By using transaction functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

But extensive use of caching in the application peers

depending on storage layer

none

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

none

But extensive use of caching in the application peers

depending on storage layer

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

Source-replica replication with hot standby and reads on replicas

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

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

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

yes

In-memory capabilities

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

yes

recommended only for testing and development

depending on storage layer

caching of (temporary) tables can be configured

User concepts

Access control

yes

depending on the DBMS used for storage

fine grained access rights 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

Nubank buys firm behind Clojure programming language
28 July 2020, Finextra

Architecting Software for Leverage
13 November 2021, InfoQ.com

TerminusDB Takes on Data Collaboration with a git-Like Approach
1 December 2020, The New Stack

James Dixon Imagines A Data Lake That Matters
26 January 2015, Forbes

Zoona Case Study
16 December 2017, AWS Blog

provided by Google News

SAP Announces Q3 2023 Results: Asia Pacific and Japan View
19 October 2023, SAP News

provided by Google News

TimescaleDB Is a Vector Database Now, Too
25 September 2023, Datanami

Timescale Acquires PopSQL to Bring a Modern, Collaborative SQL GUI to PostgreSQL Developers
4 April 2024, PR Newswire

Power IoT and time-series workloads with TimescaleDB for Azure Database for PostgreSQL
18 March 2019, Microsoft

Timescale Valuation Rockets to Over $1B with $110M Round, Marking the Explosive Rise of Time-Series Data
22 February 2022, Business Wire

Timescale announces $15M investment and new enterprise version of TimescaleDB
29 January 2019, TechCrunch

provided by Google News

Share this page