DBMS > Apache Phoenix vs. GeoMesa vs. Google Cloud Datastore vs. Snowflake

System Properties Comparison Apache Phoenix vs. GeoMesa vs. Google Cloud Datastore vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

Primary database model

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

Score	1.97
Rank	#126	Overall
	#59	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

phoenix.apache.org

www.geomesa.org

cloud.google.com/datastore

www.snowflake.com

Technical documentation

phoenix.apache.org

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

cloud.google.com/datastore/docs

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

CCRi and others

Google

Snowflake Computing Inc.

Initial release

2014

2008

2014

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

4.0.5, February 2024

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache License 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

Java

Scala

Server operating systems

Linux
Unix
Windows

hosted

Data scheme

yes

late-bound, schema-on-read capabilities

yes

schema-free

yes

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

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL-like query language (GQL)

yes

APIs and other access methods

JDBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

using Google App Engine

user defined functions

Triggers

Callbacks using the Google Apps Engine

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

depending on storage layer

Multi-source replication using Paxos

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

depending on storage layer

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

Concurrency

Support for concurrent manipulation of data

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

depending on storage layer

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

yes

depending on the DBMS used for storage

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.