DBMS > Amazon Redshift vs. Faircom DB vs. GeoMesa vs. Stardog vs. Yanza

System Properties Comparison Amazon Redshift vs. Faircom DB vs. GeoMesa vs. Stardog vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Key-value store
Relational DBMS

Spatial DBMS

Graph DBMS
RDF store

Time Series DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.20
Rank	#318	Overall
	#48	Key-value stores
	#141	Relational DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	2.02
Rank	#123	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

aws.amazon.com/redshift

www.faircom.com/products/faircom-db

www.geomesa.org

www.stardog.com

yanza.com

Technical documentation

docs.aws.amazon.com/redshift

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

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

docs.stardog.com

Developer

Amazon (based on PostgreSQL)

FairCom Corporation

CCRi and others

Stardog-Union

Yanza

Initial release

2012

1979

2014

2010

2015

Current release

V12, November 2020

4.0.5, February 2024

7.3.0, May 2020

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache License 2.0

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

ANSI C, C++

Scala

Java

Server operating systems

hosted

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

Linux
macOS
Windows

Windows

Data scheme

yes

schema free, schema optional, schema required, partial schema,

yes

schema-free and OWL/RDFS-schema support

schema-free

Typing

predefined data types such as float or date

yes

yes, ANSI SQL Types, JSON, typed binary structures

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.

Import/export of XML data possible

Secondary indexes

restricted

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes, ANSI SQL with proprietary extensions

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

JDBC
ODBC

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

in Python

yes

.Net, JavaScript, C/C++

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

depending on storage layer

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

depending on storage layer

Multi-source replication in HA-Cluster

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

depending on storage layer

Immediate Consistency in HA-Cluster

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

relationships in graphs

Transaction concepts

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

ACID

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Yes, tunable from durable to delayed durability to in-memory

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

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Fine grained access rights according to SQL-standard with additional protections for files

yes

depending on the DBMS used for storage

Access rights for users and roles

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.