DBMS > Apache Impala vs. mSQL vs. OrigoDB vs. Prometheus vs. Snowflake

System Properties Comparison Apache Impala vs. mSQL vs. OrigoDB vs. Prometheus vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph 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
Object oriented DBMS

Time Series DBMS

Relational DBMS

Secondary database models

Document store

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

Score	14.03
Rank	#40	Overall
	#24	Relational DBMS

Score	1.67
Rank	#151	Overall
	#70	Relational DBMS

Score	0.03
Rank	#378	Overall
	#51	Document stores
	#18	Object oriented DBMS

Score	7.92
Rank	#51	Overall
	#2	Time Series DBMS

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

impala.apache.org

hughestech.com.au/products/msql

origodb.com

prometheus.io

www.snowflake.com

Technical documentation

impala.apache.org/impala-docs.html

origodb.com/docs

prometheus.io/docs

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Hughes Technologies

Robert Friberg et al

Snowflake Computing Inc.

Initial release

2013

1994

2009

under the name LiveDB

2015

2014

Current release

4.1.0, June 2022

4.4, October 2021

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

free licenses can be provided

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

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Linux
Windows

hosted

Data scheme

yes

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

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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.

can be achieved using .NET

Import of XML data possible

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

APIs and other access methods

JDBC
ODBC

.NET Client API
HTTP API
LINQ

RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

user defined functions

Triggers

yes

Domain Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

client side managed; servers are not synchronized

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

none

Source-replica replication

yes

by Federation

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

query execution via MapReduce

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

none

Immediate Consistency

Foreign keys

Referential integrity

depending on model

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

Write ahead log

yes

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users, groups and roles

based on Apache Sentry and Kerberos

Role based authorization

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.