DBMS > Altibase vs. GeoMesa vs. RDF4J vs. Snowflake

System Properties Comparison Altibase vs. GeoMesa vs. RDF4J vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An enterprise grade, high-performance RDBMS

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

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

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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

Score	1.02
Rank	#189	Overall
	#88	Relational DBMS

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

github.com/ALTIBASE/Documents/tree/master/Manuals

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

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

Developer

Altibase

CCRi and others

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

Snowflake Computing Inc.

Initial release

1999

2014

2004

2014

Current release

v7.3, 2023, August 2023

5.0.0, May 2024

License

Commercial or Open Source

commercial

Open source edition discontinued with March 2023

Open Source

Apache License 2.0

Open Source

Eclipse Distribution License (EDL), v1.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

C++

Scala

Java

Server operating systems

AIX
HP-UX
Linux

Linux
OS X
Unix
Windows

hosted

Data scheme

yes

RDF Schemas

yes

support of semi-structured data formats (JSON, XML, Avro)

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.

yes

Secondary indexes

yes

SQL

Support of SQL

ANSI SQL-92

yes

APIs and other access methods

JDBC
ODBC
Proprietary protocol

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

Supported programming languages

C
C++
Java

Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

stored procedures and stored functions

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

depending on storage layer

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

In-memory capabilities

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

yes

depending on storage layer

User concepts

Access control

fine grained access rights according to SQL-standard

yes

depending on the DBMS used for storage

Users with fine-grained authorization concept, user roles and pluggable authentication

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.