DBMS > GeoMesa vs. Google Cloud Bigtable vs. Ingres vs. RDF4J

System Properties Comparison GeoMesa vs. Google Cloud Bigtable vs. Ingres vs. RDF4J

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.

Well established RDBMS

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

Primary database model

Spatial DBMS

Key-value store
Wide column store

Relational DBMS

RDF store

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	4.11
Rank	#81	Overall
	#44	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Website

www.geomesa.org

cloud.google.com/bigtable

www.actian.com/databases/ingres

rdf4j.org

Technical documentation

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

cloud.google.com/bigtable/docs

docs.actian.com/ingres

rdf4j.org/documentation

Developer

CCRi and others

Google

Actian Corporation

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Initial release

2014

2015

1974

originally developed at University Berkely in early 1970s

2004

Current release

4.0.5, February 2024

11.2, May 2022

License

Commercial or Open Source

Open Source

Apache License 2.0

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

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

Server operating systems

hosted

AIX
HP Open VMS
HP-UX
Linux
Solaris
Windows

Linux
OS X
Unix
Windows

Data scheme

yes

schema-free

yes

RDF Schemas

Typing

predefined data types such as float or date

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.

but tools for importing/exporting data from/to XML-files available

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

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

.NET Client API
JDBC
ODBC
proprietary protocol (OpenAPI)

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

Supported programming languages

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

Java
PHP
Python

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

depending on storage layer

Sharding

horizontal partitioning

Ingres Star to access multiple databases simultaneously

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

Ingres Replicator

none

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

Isolation support depends on the API used

Concurrency

Support for concurrent manipulation of data

yes

MVCC

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

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

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

Google expands BigQuery with Gemini, brings vector support to cloud databases
29 February 2024, VentureBeat

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

Google scales up Cloud Bigtable NoSQL database
27 January 2022, TechTarget

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

provided by Google News

Postgres pioneer Michael Stonebraker promises to upend the database once more
26 December 2023, The Register

New startup from Postgres creator puts the database at heart of software stack
12 March 2024, TechCrunch

Actian Launches Ingres as a Fully-Managed Cloud Service
24 September 2021, Integration Developers

PostgreSQL now top developer choice ahead of MySQL, according to massive new survey • DEVCLASS
13 June 2023, DevClass

Dr. Michael Stonebraker: A Short History of Database Systems
1 February 2019, The New Stack

provided by Google News

GraphDB Goes Open Source
27 January 2020, iProgrammer

provided by Google News

Share this page