DBMS > Drizzle vs. PostGIS vs. SAP Adaptive Server vs. Snowflake vs. TerminusDB

System Properties Comparison Drizzle vs. PostGIS vs. SAP Adaptive Server vs. Snowflake vs. TerminusDB

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.

Spatial extension of PostgreSQL

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

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Secondary database models

Relational DBMS

Spatial DBMS

with Boeing's Spatial Query Server

Document store
RDF store

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

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	35.09
Rank	#25	Overall
	#17	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	0.23
Rank	#316	Overall
	#27	Graph DBMS

Website

postgis.net

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

www.snowflake.com

terminusdb.com

Technical documentation

postgis.net/documentation

help.sap.com/docs/SAP_ASE

docs.snowflake.net/manuals/index.html

terminusdb.github.io/terminusdb/#

Developer

Drizzle project, originally started by Brian Aker

SAP, Sybase

Snowflake Computing Inc.

DataChemist Ltd.

Initial release

2008

2005

1987

2014

2018

Current release

7.2.4, September 2012

3.4.2, February 2024

16.0

11.0.0, January 2023

License

Commercial or Open Source

Open Source

GNU GPL

Open Source

GPL v2.0

commercial

Open Source

GPL V3

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

C and C++

Prolog, Rust

Server operating systems

FreeBSD
Linux
OS X

AIX
HP-UX
Linux
Solaris
Unix
Windows

hosted

Linux

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

SQL-like query language (WOQL)

APIs and other access methods

JDBC

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

CLI Client
JDBC
ODBC

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

C
C++
Java
PHP

C
C++
Cobol
Java
Java
Perl
PHP
Python

JavaScript (Node.js)
Python

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

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

yes

based on PostgreSQL

horizontal partitioning

yes

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

Multi-source replication
Source-replica replication

yes

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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 journaling

In-memory capabilities

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

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

yes

based on PostgreSQL

fine grained access rights according to SQL-standard

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

Role-based access control

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.