DBMS > GeoMesa vs. Google Cloud Bigtable vs. Sadas Engine vs. XTDB

System Properties Comparison GeoMesa vs. Google Cloud Bigtable vs. Sadas Engine vs. XTDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Google's NoSQL Big Data database service. It's the same database that powers many core Google services, including Search, Analytics, Maps, and Gmail.

SADAS Engine is a columnar DBMS specifically designed for high performance in data warehouse environments

A general purpose database with bitemporal SQL and Datalog and graph queries

Primary database model

Spatial DBMS

Key-value store
Wide column store

Relational DBMS

Document store

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

Score	0.81
Rank	#214	Overall
	#4	Spatial DBMS

Score	3.58
Rank	#92	Overall
	#14	Key-value stores
	#8	Wide column stores

Score	0.03
Rank	#379	Overall
	#156	Relational DBMS

Score	0.09
Rank	#351	Overall
	#47	Document stores

Website

www.geomesa.org

cloud.google.com/bigtable

www.sadasengine.com

github.com/xtdb/xtdb
www.xtdb.com

Technical documentation

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

cloud.google.com/bigtable/docs

www.sadasengine.com/en/sadas-engine-download-free-trial-and-documentation/#documentation

www.xtdb.com/docs

Developer

CCRi and others

Google

SADAS s.r.l.

Juxt Ltd.

Initial release

2014

2015

2006

2019

Current release

4.0.5, February 2024

8.0

1.19, September 2021

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

free trial version available

Open Source

MIT License

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++

Clojure

Server operating systems

hosted

AIX
Linux
Windows

All OS with a Java 8 (and higher) VM
Linux

Data scheme

yes

schema-free

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, extensible-data-notation format

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.

Secondary indexes

yes

SQL

Support of SQL

yes

limited SQL, making use of Apache Calcite

APIs and other access methods

gRPC (using protocol buffers) API
HappyBase (Python library)
HBase compatible API (Java)

JDBC
ODBC
Proprietary protocol

HTTP REST
JDBC

Supported programming languages

C#
C++
Go
Java
JavaScript (Node.js)
Python

.Net
C
C#
C++
Groovy
Java
PHP
Python

Clojure
Java

Server-side scripts

Stored procedures

Triggers

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

depending on storage layer

Internal replication in Colossus, and regional replication between two clusters in different zones

none

yes, each node contains all data

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

depending on storage layer

Immediate consistency (for a single cluster), Eventual consistency (for two or more replicated clusters)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic single-row operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, flexibel persistency by using storage technologies like Apache Kafka, RocksDB or LMDB

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

depending on storage layer

yes

managed by 'Learn by Usage'

User concepts

Access control

yes

depending on the DBMS used for storage

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

Access rights for users, groups and roles 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.

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

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

What is Google Bigtable? | Definition from TechTarget
1 March 2022, TechTarget

Google Introduces Autoscaling for Cloud Bigtable for Optimizing Costs
31 January 2022, InfoQ.com

Review: Google Bigtable scales with ease
7 September 2016, InfoWorld

Google Cloud makes it cheaper to run smaller workloads on Bigtable
7 April 2020, TechCrunch

provided by Google News

Share this page