DBMS > FileMaker vs. Geode vs. Memcached vs. RocksDB vs. Teradata Aster

System Properties Comparison FileMaker vs. Geode vs. Memcached vs. RocksDB vs. Teradata Aster

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

In-memory key-value store, originally intended for caching

Embeddable persistent key-value store optimized for fast storage (flash and RAM)

Platform for big data analytics on multistructured data sources and types

Primary database model

Relational DBMS

Key-value store

Relational DBMS

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

Score	47.91
Rank	#20	Overall
	#14	Relational DBMS

Score	1.86
Rank	#134	Overall
	#24	Key-value stores

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	3.41
Rank	#86	Overall
	#11	Key-value stores

Website

www.claris.com/filemaker

geode.apache.org

www.memcached.org

rocksdb.org

Technical documentation

www.claris.com/resources/documentation

geode.apache.org/docs

github.com/memcached/memcached/wiki

github.com/facebook/rocksdb/wiki

Developer

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.

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Facebook, Inc.

Teradata

Initial release

1983

2002

2003

2013

2005

Current release

19.4.1, November 2021

1.1, February 2017

1.6.27, May 2024

9.2.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

BSD license

Open Source

BSD

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

C++

Server operating systems

iOS

client part only
Linux
OS X
Windows

All OS with a Java VM

the JDK (8 or later) is also required

FreeBSD
Linux
OS X
Unix
Windows

Linux

Data scheme

yes

schema-free

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

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

yes

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

via plugins

SQL-like query language (OQL)

yes

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

Java Client API
Memcached protocol
RESTful HTTP API

Proprietary protocol

C++ API
Java API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

PHP

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

C
C++
Go
Java
Perl
Python
Ruby

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

user defined functions

R packages

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

Multi-source replication

none

Repcached, a Memcached patch, provides this functionallity

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes, on a single node

yes

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.

yes

User concepts

Access control

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

Access rights per client and object definable

yes

using SASL (Simple Authentication and Security Layer) protocol

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.