DBMS > Citus vs. MarkLogic vs. Prometheus vs. Snowflake

System Properties Comparison Citus vs. MarkLogic vs. Prometheus 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

Operational and transactional Enterprise NoSQL database

Open-source Time Series DBMS and monitoring system

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

Primary database model

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Time Series DBMS

Relational DBMS

Secondary database models

Document store

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

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	8.42
Rank	#47	Overall
	#2	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

docs.citusdata.com

docs.marklogic.com

prometheus.io/docs

docs.snowflake.net/manuals/index.html

Developer

MarkLogic Corp.

Snowflake Computing Inc.

Initial release

2010

2001

2015

2014

Current release

8.1, December 2018

11.0, December 2022

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

commercial

restricted free version is available

Open Source

Apache 2.0

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

Server operating systems

Linux

Linux
OS X
Windows

Linux
Windows

hosted

Data scheme

yes

schema-free

Schema can be enforced

yes

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

Typing

predefined data types such as float or date

yes

Numeric data only

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

yes

Import of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

yes

SQL92

yes

APIs and other access methods

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

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

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

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

.Net
C++
Go
Haskell
Java
JavaScript (Node.js)
Python
Ruby

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.

yes

via XQuery or JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

yes

by Federation

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA 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.

yes, with Range Indexes

User concepts

Access control

fine grained access rights according to SQL-standard

Role-based access control at the document and subdocument levels

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.