DBMS > BigObject vs. Greenplum vs. Ignite vs. Snowflake

System Properties Comparison BigObject vs. Greenplum vs. Ignite vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

Analytic Database platform built on PostgreSQL. Full name is Pivotal Greenplum Database

A logical database in Greenplum is an array of individual PostgreSQL databases working together to present a single database image.

Apache Ignite is a memory-centric distributed database, caching, and processing platform for transactional, analytical, and streaming workloads, delivering in-memory speeds at petabyte scale.

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

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Key-value store
Relational DBMS

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	3.16
Rank	#96	Overall
	#15	Key-value stores
	#49	Relational DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

Technical documentation

docs.bigobject.io

docs.greenplum.org

apacheignite.readme.io/docs

docs.snowflake.net/manuals/index.html

Developer

BigObject, Inc.

Pivotal Software Inc.

Apache Software Foundation

Snowflake Computing Inc.

Initial release

2015

2005

2015

2014

Current release

7.0.0, September 2023

Apache Ignite 2.6

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache 2.0

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

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Linux

Linux
OS X
Solaris
Windows

hosted

Data scheme

yes

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

Typing

predefined data types such as float or date

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

since Version 4.2

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like DML and DDL statements

yes

ANSI-99 for query and DML statements, subset of DDL

yes

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

JDBC
ODBC

HDFS API
Hibernate
JCache
JDBC
ODBC
Proprietary protocol
RESTful HTTP API
Spring Data

CLI Client
JDBC
ODBC

Supported programming languages

C
Java
Perl
Python
R

C#
C++
Java
PHP
Python
Ruby
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

Lua

yes

yes (compute grid and cache interceptors can be used instead)

user defined functions

Triggers

yes

yes (cache interceptors and events)

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes (replicated cache)

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

yes (compute grid and hadoop accelerator)

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

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

User concepts

Access control

fine grained access rights according to SQL-standard

Security Hooks for custom implementations

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.