DBMS > Apache Jena - TDB vs. GeoMesa vs. Google Cloud Bigtable vs. SAP Advantage Database Server

System Properties Comparison Apache Jena - TDB vs. GeoMesa vs. Google Cloud Bigtable vs. SAP Advantage Database Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A RDF storage and query DBMS, shipped as an optional-use component of the Apache Jena framework

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.

Low-cost RDBMS with access to ISAM and FoxPro data structures

Primary database model

RDF store

Spatial DBMS

Key-value store
Wide column store

Relational DBMS

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

Score	3.62
Rank	#83	Overall
	#3	RDF stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	3.15
Rank	#95	Overall
	#14	Key-value stores
	#8	Wide column stores

Website

jena.apache.org/documentation/tdb/index.html

www.geomesa.org

cloud.google.com/bigtable

www.sap.com/products/advantage-database-server.html

Technical documentation

jena.apache.org/documentation/tdb/index.html

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

cloud.google.com/bigtable/docs

Developer

Apache Software Foundation

originally developed by HP Labs

CCRi and others

Google

Sybase, SAP

Initial release

2000

2014

2015

1993

Current release

4.9.0, July 2023

5.0.0, May 2024

License

Commercial or Open Source

Open Source

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

All OS with a Java VM

hosted

Linux
Windows

Data scheme

yes

RDF Schemas

yes

schema-free

yes

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.

Secondary indexes

yes

SQL

Support of SQL

yes

APIs and other access methods

Fuseki

REST-style SPARQL HTTP Interface
Jena RDF API
RIO

RDF Input/Output

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

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

Java

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

Delphi
Perl
PHP

Server-side scripts

Stored procedures

yes

Triggers

yes

via event handler

yes

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

depending on storage layer

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

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
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)

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

TDB Transactions

Atomic single-row operations

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.

depending on storage layer

caching of (temporary) tables can be configured

User concepts

Access control

Access control via Jena Security

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

Sparql Secrets In Jena-Fuseki - DataScienceCentral.com
24 July 2022, Data Science Central

Extract and query knowledge graphs using Apache Jena (SPARQL Engine)
4 December 2019, Towards Data Science

6 Java Libraries for Machine Learning – AIM
3 October 2023, Analytics India Magazine

A catalogue with semantic annotations makes multilabel datasets FAIR | Scientific Reports
4 May 2022, Nature.com

MarkLogic Hones Its Triple Store
18 August 2015, Datanami

provided by Google News

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

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

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

provided by Google News

SAP Announces Q3 2023 Results: Asia Pacific and Japan View
19 October 2023, SAP News

provided by Google News

Share this page