DBMS > Citus vs. EsgynDB vs. Manticore Search vs. Snowflake

System Properties Comparison Citus vs. EsgynDB vs. Manticore Search vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

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

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

Primary database model

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Document store

Time Series DBMS

using the Manticore Columnar Library

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

Score	1.96
Rank	#119	Overall
	#58	Relational DBMS

Score	0.15
Rank	#325	Overall
	#145	Relational DBMS

Score	0.23
Rank	#300	Overall
	#21	Search engines

Score	142.50
Rank	#7	Overall
	#5	Relational DBMS

Website

Technical documentation

docs.citusdata.com

manual.manticoresearch.com

docs.snowflake.net/manuals/index.html

Developer

Esgyn

Manticore Software

Snowflake Computing Inc.

Initial release

2010

2015

2017

2014

Current release

8.1, December 2018

6.0, February 2023

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

Open Source

GPL version 2

commercial

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

C++

Server operating systems

Linux

FreeBSD
Linux
macOS
Windows

hosted

Data scheme

yes

Fixed schema

yes

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

Typing

predefined data types such as float or date

yes

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

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

specific XML type available, but no XML query functionality

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

standard, with numerous extensions

yes

SQL-like query language

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC

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

CLI Client
JDBC
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

All languages supporting JDBC/ODBC/ADO.Net

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Java Stored Procedures

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

Multi-source replication between multi datacenters

Synchronous replication based on Galera library

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

yes

In-memory capabilities

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

User concepts

Access control

fine grained access rights according to SQL-standard

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

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.