DBMS > Alibaba Cloud AnalyticDB for PostgreSQL vs. EJDB vs. GeoMesa vs. Google BigQuery vs. HEAVY.AI

System Properties Comparison Alibaba Cloud AnalyticDB for PostgreSQL vs. EJDB vs. GeoMesa vs. Google BigQuery vs. HEAVY.AI

Editorial information provided by DB-Engines

Name

Description

An online MPP (Massively Parallel Processing) data warehousing service based on Greenplum

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Large scale data warehouse service with append-only tables

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

Primary database model

Secondary database models

Spatial DBMS

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

Score	0.76
Rank	#220	Overall
	#102	Relational DBMS

Score	0.31
Rank	#296	Overall
	#44	Document stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.64
Rank	#145	Overall
	#67	Relational DBMS

Website

www.alibabacloud.com/product/hybriddb-postgresql

github.com/Softmotions/ejdb

www.geomesa.org

cloud.google.com/bigquery

github.com/heavyai/heavydb
www.heavy.ai

Technical documentation

www.alibabacloud.com/help/en/analyticdb-for-postgresql/latest/product-introduction-overview

github.com/Softmotions/ejdb/blob/master/README.md

www.geomesa.org/documentation/stable/user/index.html

cloud.google.com/bigquery/docs

docs.heavy.ai

Developer

Alibaba / Pivotal Software Inc. / PostgreSQL Global Development Group

Softmotions

CCRi and others

Google

HEAVY.AI, Inc.

Initial release

2016

2012

2014

2010

2016

Current release

5.0.0, May 2024

5.10, January 2022

License

Commercial or Open Source

commercial

Open Source

GPLv2

Open Source

Apache License 2.0

commercial

Open Source

Apache Version 2; enterprise edition available

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

Scala

C++ and CUDA

Server operating systems

hosted

server-less

hosted

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

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

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

JDBC
ODBC

in-process shared library

RESTful HTTP/JSON API

JDBC
ODBC
Thrift
Vega

Supported programming languages

C
Java
Perl
Python
R

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

All languages supporting JDBC/ODBC/Thrift
Python

Server-side scripts

Stored procedures

yes

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Implicit feature of the cloud service

none

depending on storage layer

none

Sharding

Round robin

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Implicit feature of the cloud service

none

depending on storage layer

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

ACID

Since BigQuery is designed for querying data

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

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.

depending on storage layer

yes

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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

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.