DBMS > BigObject vs. Google BigQuery vs. Greenplum vs. Solr

System Properties Comparison BigObject vs. Google BigQuery vs. Greenplum vs. Solr

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

Large scale data warehouse service with append-only tables

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.

A widely used distributed, scalable search engine based on Apache Lucene

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Relational DBMS

Search engine

Secondary database models

Document store
Spatial DBMS

Spatial DBMS

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

Score	0.13
Rank	#333	Overall
	#147	Relational DBMS

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	8.37
Rank	#48	Overall
	#30	Relational DBMS

Score	42.91
Rank	#24	Overall
	#3	Search engines

Website

bigobject.io

cloud.google.com/bigquery

greenplum.org

solr.apache.org

Technical documentation

docs.bigobject.io

cloud.google.com/bigquery/docs

docs.greenplum.org

solr.apache.org/resources.html

Developer

BigObject, Inc.

Google

Pivotal Software Inc.

Apache Software Foundation

Initial release

2015

2010

2005

2006

Current release

7.0.0, September 2023

9.6.0, April 2024

License

Commercial or Open Source

commercial

free community edition available

commercial

Open Source

Apache 2.0

Open Source

Apache Version 2

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

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

hosted

Linux

All OS with a Java VM

runs as a servlet in servlet container (e.g. Tomcat, Jetty is included)

Data scheme

yes

Dynamic Fields enables on-the-fly addition of new fields

Typing

predefined data types such as float or date

yes

supports customizable data types and automatic typing

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

All search fields are automatically indexed

SQL

Support of SQL

SQL-like DML and DDL statements

yes

Solr Parallel SQL Interface

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

JDBC
ODBC

Java API
RESTful HTTP/JSON API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C
Java
Perl
Python
R

.Net
Erlang
Java
JavaScript
any language that supports sockets and either XML or JSON
Perl
PHP
Python
Ruby
Scala

Server-side scripts

Stored procedures

Lua

user defined functions

in JavaScript

yes

Java plugins

Triggers

yes

User configurable commands triggered on index changes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Source-replica replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

spark-solr: github.com/lucidworks/spark-solr and streaming expressions to reduce

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual 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

Since BigQuery is designed for querying data

ACID

optimistic locking

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

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

yes

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.