DBMS > GeoMesa vs. Google Cloud Bigtable vs. NSDb vs. Tibero

System Properties Comparison GeoMesa vs. Google Cloud Bigtable vs. NSDb vs. Tibero

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.

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

A secure RDBMS, designed for easy portability from Oracle

Primary database model

Spatial DBMS

Key-value store
Wide column store

Time Series DBMS

Relational DBMS

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	3.26
Rank	#92	Overall
	#13	Key-value stores
	#8	Wide column stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	1.78
Rank	#140	Overall
	#64	Relational DBMS

Website

www.geomesa.org

cloud.google.com/bigtable

nsdb.io

us.tmaxsoft.com/products/tibero

Technical documentation

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

cloud.google.com/bigtable/docs

nsdb.io/Architecture

technet.tmaxsoft.com/upload/download/online/tibero/pver-20150504-000002/index.html

Developer

CCRi and others

Google

TmaxSoft

Initial release

2014

2015

2017

2003

Current release

4.0.5, February 2024

6, April 2015

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

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

Scala

Java, Scala

C and Assembler

Server operating systems

hosted

Linux
macOS

AIX
HP-UX
Linux
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

APIs and other access methods

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

gRPC
HTTP REST
WebSocket

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)
Tibero CLI

Supported programming languages

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

Java
Scala

C
C#
C++
Cobol
Java
Objective-C
Perl
PHP
Python
Ruby
Visual Basic

Server-side scripts

Stored procedures

Persistent Stored Procedure (PSM)

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

by range, hash, list or composite

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

Multi-source replication
Source-replica replication

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)

Eventual Consistency

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

Using Apache Lucene

yes

In-memory capabilities

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

depending on storage layer

planned for next version

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)

fine grained access rights according to SQL-standard (SQL 92, SQL 99)

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 announces Axion, its first Arm-based CPU for data centers
9 April 2024, Yahoo Movies Canada

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

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

provided by Google News

ArkData to Officially Support Domestic Database 'Tibero 7'
23 April 2024, BusinessKorea

How to Succeed at Large-Scale Mainframe Replatforming with TmaxSoft OpenFrame on AWS | Amazon Web Services
2 August 2022, AWS Blog

ArkData's 'Ark for CDC' supports real-time data extraction and replication for Tibero DBMS.
18 April 2023, BusinessKorea

Tmax deploys advanced database management system at UITM's disaster recovery site
30 December 2022, The Malaysian Reserve

Open-source DBMS becoming battleground of public cloud
17 May 2022, Etnews

provided by Google News

Share this page