DBMS > Citus vs. GeoMesa vs. Google Cloud Datastore vs. STSdb

System Properties Comparison Citus vs. GeoMesa vs. Google Cloud Datastore vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable hybrid operational and analytics RDBMS for big data use cases based on PostgreSQL

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Secondary database models

Document store

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

Score	2.21
Rank	#118	Overall
	#56	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

www.citusdata.com

www.geomesa.org

cloud.google.com/datastore

github.com/STSSoft/STSdb4

Technical documentation

docs.citusdata.com

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

cloud.google.com/datastore/docs

Developer

CCRi and others

Google

STS Soft SC

Initial release

2010

2014

2008

2011

Current release

8.1, December 2018

4.0.5, February 2024

4.0.8, September 2015

License

Commercial or Open Source

Open Source

AGPL, commercial license also available

Open Source

Apache License 2.0

commercial

Open Source

GPLv2, commercial license 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

Server operating systems

Linux

hosted

Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

yes

primitive types and user defined types (classes)

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

specific XML type available, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

yes

standard, with numerous extensions

SQL-like query language (GQL)

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

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

.NET Client API

Supported programming languages

.Net
C
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

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

C#
Java

Server-side scripts

Stored procedures

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

using Google App Engine

Triggers

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

other methods possible by using 3rd party extensions

depending on storage layer

Multi-source replication using Paxos

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate 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.

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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.

depending on storage layer

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Ubicloud wants to build an open source alternative to AWS
5 March 2024, TechCrunch

Ubicloud reels in $16M for its open-source cloud platform
5 March 2024, SiliconANGLE News

Microsoft acquires Citus Data, re-affirming its commitment to Open Source and accelerating Azure PostgreSQL ...
24 January 2019, blogs.microsoft.com

Microsoft Benchmarks Distributed PostgreSQL DBs
10 July 2023, Datanami

Distributed PostgreSQL Benchmarks: Azure Cosmos DB, CockroachDB, and YugabyteDB
8 July 2023, InfoQ.com

provided by Google News

Best cloud storage of 2024
21 May 2024, TechRadar

Google Cloud Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

Share this page