DBMS > Apache Impala vs. OrigoDB vs. RisingWave vs. Snowflake

System Properties Comparison Apache Impala vs. OrigoDB vs. RisingWave vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for Hadoop

A fully ACID in-memory object graph database

A distributed RDBMS for stream processing, wire-compatible with PostgreSQL

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

Primary database model

Relational DBMS

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store

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

Score	12.45
Rank	#40	Overall
	#24	Relational DBMS

Score	0.06
Rank	#380	Overall
	#50	Document stores
	#19	Object oriented DBMS

Score	0.64
Rank	#238	Overall
	#110	Relational DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

impala.apache.org

origodb.com

www.risingwave.com/database

www.snowflake.com

Technical documentation

impala.apache.org/impala-docs.html

origodb.com/docs

docs.risingwave.com/docs/current/intro

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Cloudera

Robert Friberg et al

RisingWave Labs

Snowflake Computing Inc.

Initial release

2013

2009

under the name LiveDB

2022

2014

Current release

4.1.0, June 2022

1.2, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2

Open Source

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

Rust

Server operating systems

Linux

Linux
Windows

Docker
Linux
macOS

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

Standard SQL-types and JSON

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

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

JDBC
ODBC

.NET Client API
HTTP API
LINQ

JDBC
PostgreSQL wire protocol

CLI Client
JDBC
ODBC

Supported programming languages

All languages supporting JDBC/ODBC

.Net

Go
Java
JavaScript (Node.js)
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions and integration of map-reduce

yes

UDFs in Python or Java

user defined functions

Triggers

yes

Domain Events

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

horizontal partitioning

client side managed; servers are not synchronized

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

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

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 and Roles

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.