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

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

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

Cloud-based data warehousing service for structured and semi-structured data

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

Primary database model

Relational DBMS

Spatial DBMS

Relational DBMS

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	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.17
Rank	#334	Overall
	#148	Relational DBMS

Website

www.geomesa.org

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

www.snowflake.com

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

Technical documentation

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

help.sap.com/docs/SAP_ASE

docs.snowflake.net/manuals/index.html

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

Developer

Drizzle project, originally started by Brian Aker

CCRi and others

SAP, Sybase

Snowflake Computing Inc.

Transaction Software GmbH

Initial release

2008

2014

1987

2014

1987

Current release

7.2.4, September 2012

5.0.0, May 2024

16.0

Transbase 8.3, 2022

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

Apache License 2.0

commercial

free development license

Cloud-based only

Only available as a cloud service

yes

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++

Server operating systems

FreeBSD
Linux
OS X

AIX
HP-UX
Linux
Solaris
Unix
Windows

hosted

FreeBSD
Linux
macOS
Solaris
Windows

Data scheme

yes

support of semi-structured data formats (JSON, XML, Avro)

yes

Typing

predefined data types such as float or date

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

with proprietary extensions

yes

APIs and other access methods

JDBC

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

CLI Client
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C
C++
Java
PHP

C
C++
Cobol
Java
Java
Perl
PHP
Python

JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

Java and Transact-SQL

user defined functions

yes

Triggers

hooks for callbacks inside the server can be used.

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

horizontal partitioning

yes

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

yes

Source-replica replication

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

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.

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

Users with fine-grained authorization concept, user roles and pluggable authentication

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.