DBMS > Amazon Redshift vs. Dgraph vs. FileMaker vs. Geode vs. Heroic

System Properties Comparison Amazon Redshift vs. Dgraph vs. FileMaker vs. Geode vs. Heroic

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Distributed and scalable native Graph DBMS

FileMaker is a cross-platform RDBMS that includes a GUI frontend.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Primary database model

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.45
Rank	#156	Overall
	#15	Graph DBMS

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	1.92
Rank	#131	Overall
	#23	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Website

aws.amazon.com/redshift

dgraph.io

www.claris.com/filemaker

geode.apache.org

github.com/spotify/heroic

Technical documentation

docs.aws.amazon.com/redshift

dgraph.io/docs

www.claris.com/resources/documentation

geode.apache.org/docs

spotify.github.io/heroic

Developer

Amazon (based on PostgreSQL)

Dgraph Labs, Inc.

Claris

a subsidiary of Apple

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

Spotify

Initial release

2012

2016

1983

2002

2014

Current release

19.4.1, November 2021

1.1, February 2017

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

Apache 2.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

Java

Server operating systems

hosted

Linux
OS X
Windows

iOS

client part only
Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

Data scheme

yes

schema-free

yes

schema-free

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

A http query request can return the data in XML format

Secondary indexes

restricted

yes

via Elasticsearch

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

via plugins

SQL-like query language (OQL)

APIs and other access methods

JDBC
ODBC

GraphQL query language
gRPC (using protocol buffers) API
HTTP API

Filemaker WebDirect
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Supported programming languages

All languages supporting JDBC/ODBC

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

PHP

.Net
All JVM based languages
C++
Groovy
Java
Scala

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication via Raft

Source-replica replication, warm standby

since Version 14

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

yes, on a single node

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Planned for future releases

simple rights management via user accounts and connection to external directory services

Access rights per client and object definable

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.