DBMS > Amazon Redshift vs. Datomic vs. Drizzle vs. Manticore Search

System Properties Comparison Amazon Redshift vs. Datomic vs. Drizzle vs. Manticore Search

Please select another system to include it in the comparison.

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

Large scale data warehouse service for use with business intelligence tools

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

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

Multi-storage database for search, including full-text search.

Primary database model

Relational DBMS

Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	1.66
Rank	#144	Overall
	#66	Relational DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Website

aws.amazon.com/redshift

www.datomic.com

manticoresearch.com

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

manual.manticoresearch.com

Developer

Amazon (based on PostgreSQL)

Cognitect

Drizzle project, originally started by Brian Aker

Manticore Software

Initial release

2012

2008

2017

Current release

1.0.7075, December 2023

7.2.4, September 2012

6.0, February 2023

License

Commercial or Open Source

commercial

limited edition free

Open Source

GNU GPL

Open Source

GPL version 2

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

Java, Clojure

C++

Server operating systems

hosted

All OS with a Java VM

FreeBSD
Linux
OS X

FreeBSD
Linux
macOS
Windows

Data scheme

yes

Fixed schema

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

Secondary indexes

restricted

yes

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

with proprietary extensions

SQL-like query language

APIs and other access methods

JDBC
ODBC

RESTful HTTP API

JDBC

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

C
C++
Java
PHP

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

user defined functions

Triggers

By using transaction functions

hooks for callbacks inside the server can be used.

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

Multi-source replication
Source-replica replication

Synchronous replication based on Galera library

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

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

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

The original contents of fields are not stored in the Manticore index.

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

User concepts

Access control

fine grained access rights according to SQL-standard

Pluggable authentication mechanisms

e.g. LDAP, HTTP

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.