DBMS > Drizzle vs. GeoMesa vs. SAP Adaptive Server vs. Transbase vs. XTDB

System Properties Comparison Drizzle vs. GeoMesa vs. SAP Adaptive Server vs. Transbase vs. XTDB

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

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

The SAP (Sybase) Adaptive Server Enterprise (ASE) is an enterprise-class RDBMS

A resource-optimized, high-performance, universally applicable RDBMS

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Secondary database models

Spatial DBMS

with Boeing's Spatial Query Server

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

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	35.09
Rank	#25	Overall
	#17	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Score	0.18
Rank	#332	Overall
	#46	Document stores

Website

www.geomesa.org

www.sap.com/products/technology-platform/sybase-ase.html

www.transaction.de/en/products/transbase.html

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

help.sap.com/docs/SAP_ASE

www.transaction.de/en/products/transbase/features.html

www.xtdb.com/docs

Developer

Drizzle project, originally started by Brian Aker

CCRi and others

SAP, Sybase

Transaction Software GmbH

Juxt Ltd.

Initial release

2008

2014

1987

2019

Current release

7.2.4, September 2012

5.0.0, May 2024

16.0

Transbase 8.3, 2022

1.19, September 2021

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache License 2.0

commercial

free development license

Open Source

MIT License

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

C++

Scala

C and C++

Clojure

Server operating systems

FreeBSD
Linux
OS X

AIX
HP-UX
Linux
Solaris
Unix
Windows

FreeBSD
Linux
macOS
Solaris
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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

with proprietary extensions

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST
JDBC

Supported programming languages

C
C++
Java
PHP

C
C++
Cobol
Java
Java
Perl
PHP
Python

C
C#
C++
Java
JavaScript
Kotlin
Objective-C
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

Java and Transact-SQL

yes

Triggers

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

Multi-source replication
Source-replica replication

Source-replica replication

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

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

depending on storage layer

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Achieve zero RPO for your SAP ASE (Sybase) databases with Amazon FSx for NetApp ONTAP | Amazon Web Services
7 May 2024, AWS Blog

New Services for SAP HANA Cloud Database
7 April 2021, SAP News

Install latest SAP Adaptive Server Enterprise patches, experts urge
3 June 2020, CSO Online

Patch SAP Adaptive Server Enterprise now to avoid takeover risk
3 June 2020, BleepingComputer

AWS Launch Wizard is now available in Melbourne, Spain, and Zurich Regions
26 January 2024, AWS Blog

provided by Google News

Share this page