DBMS > Drizzle vs. EsgynDB vs. Sequoiadb vs. TimescaleDB vs. Ultipa

System Properties Comparison Drizzle vs. EsgynDB vs. Sequoiadb vs. TimescaleDB vs. Ultipa

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.

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

NewSQL database with distributed OLTP and SQL

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

High performance Graph DBMS supporting HTAP high availability cluster deployment

Primary database model

Relational DBMS

Document store
Relational DBMS

Time Series DBMS

Graph DBMS

Secondary database models

Relational DBMS

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

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	0.42
Rank	#263	Overall
	#41	Document stores
	#121	Relational DBMS

Score	4.06
Rank	#73	Overall
	#5	Time Series DBMS

Score	0.11
Rank	#338	Overall
	#32	Graph DBMS

Website

Technical documentation

www.sequoiadb.com/en/index.php?m=Files&a=index

docs.timescale.com

www.ultipa.com/document

Developer

Drizzle project, originally started by Brian Aker

Esgyn

Sequoiadb Ltd.

Timescale

Ultipa

Initial release

2008

2015

2013

2017

2019

Current release

7.2.4, September 2012

2.15.0, May 2024

License

Commercial or Open Source

Open Source

GNU GPL

commercial

Open Source

Server: AGPL; Client: Apache V2

Open Source

Apache 2.0

commercial

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

C++, Java

C++

Server operating systems

FreeBSD
Linux
OS X

Linux

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

oid, date, timestamp, binary, regex

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

with proprietary extensions

yes

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

JDBC

ADO.NET
JDBC
ODBC

proprietary protocol using JSON

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

RESTful HTTP API

Supported programming languages

C
C++
Java
PHP

All languages supporting JDBC/ODBC/ADO.Net

.Net
C++
Java
PHP
Python

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

C++
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Java Stored Procedures

JavaScript

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

hooks for callbacks inside the server can be used.

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Multi-source replication between multi datacenters

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

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

Support to ensure data integrity after non-atomic manipulations of data

ACID

Document is locked during a transaction

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.

User concepts

Access control

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

simple password-based access control

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

Recent citations in the news

General availability: Latest version of the TimeScaleDB extension on Azure Database for PostgreSQL - Flexible Server
8 May 2024, azure.microsoft.com

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

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

PostgreSQL is Now Faster than Pinecone, 75% Cheaper, with New Open Source Extensions
11 June 2024, PR Newswire

TimescaleDB goes distributed; implements ‘Chunking’ over ‘Sharding’ for scaling-out
22 August 2019, Packt Hub

provided by Google News

Ultipa, Inc. Announces Key Updates to Its Global Partnership Program
21 August 2024, EIN News

provided by Google News

Share this page