DBMS > BigObject vs. Graph Engine vs. Ingres vs. SiriDB vs. Snowflake

System Properties Comparison BigObject vs. Graph Engine vs. Ingres vs. SiriDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

Well established RDBMS

Open Source Time Series DBMS

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Graph DBMS
Key-value store

Relational DBMS

Time Series DBMS

Relational DBMS

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

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	0.67
Rank	#232	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	3.80
Rank	#82	Overall
	#44	Relational DBMS

Score	0.07
Rank	#378	Overall
	#42	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

bigobject.io

www.graphengine.io

www.actian.com/databases/ingres

siridb.com

www.snowflake.com

Technical documentation

docs.bigobject.io

www.graphengine.io/docs/manual

docs.actian.com/ingres

docs.siridb.com

docs.snowflake.net/manuals/index.html

Developer

BigObject, Inc.

Microsoft

Actian Corporation

Cesbit

Snowflake Computing Inc.

Initial release

2015

2010

1974

originally developed at University Berkely in early 1970s

2017

2014

Current release

11.2, May 2022

License

Commercial or Open Source

commercial

free community edition available

Open Source

MIT License

commercial

Open Source

MIT License

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

.NET and C

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

.NET

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux

hosted

Data scheme

yes

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

Typing

predefined data types such as float or date

yes

Numeric data

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.

but tools for importing/exporting data from/to XML-files available

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

RESTful HTTP API

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

HTTP API

CLI Client
JDBC
ODBC

Supported programming languages

C#
C++
F#
Visual Basic

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
R

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

Ingres Star to access multiple databases simultaneously

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Ingres Replicator

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

yes

MVCC

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

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

fine grained access rights according to SQL-standard

simple rights management via user accounts

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.