DBMS > Elasticsearch vs. FileMaker vs. Google Cloud Datastore vs. LMDB vs. RocksDB

System Properties Comparison Elasticsearch vs. FileMaker vs. Google Cloud Datastore vs. LMDB vs. RocksDB

Editorial information provided by DB-Engines

Name

Description

A distributed, RESTful modern search and analytics engine based on Apache Lucene

Elasticsearch lets you perform and combine many types of searches such as structured, unstructured, geo, and metric

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

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

A high performant, light-weight, embedded key-value database library

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

Primary database model

Secondary database models

Document store
Spatial DBMS
Vector DBMS

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

Score	132.83
Rank	#7	Overall
	#1	Search engines

Score	47.91
Rank	#20	Overall
	#14	Relational DBMS

Score	4.36
Rank	#72	Overall
	#12	Document stores

Score	2.09
Rank	#121	Overall
	#20	Key-value stores

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

Website

www.elastic.co/elasticsearch

www.claris.com/filemaker

cloud.google.com/datastore

www.symas.com/symas-embedded-database-lmdb

rocksdb.org

Technical documentation

www.elastic.co/guide/en/elasticsearch/reference/current/index.html

www.claris.com/resources/documentation

cloud.google.com/datastore/docs

www.lmdb.tech/doc

github.com/facebook/rocksdb/wiki

Developer

Elastic

Claris

a subsidiary of Apple

Google

Symas

Facebook, Inc.

Initial release

2010

1983

2008

2011

2013

Current release

8.6, January 2023

19.4.1, November 2021

0.9.32, January 2024

9.2.1, May 2024

License

Commercial or Open Source

Open Source

Elastic License

commercial

Open Source

BSD

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

C++

Server operating systems

All OS with a Java VM

iOS

client part only
Linux
OS X
Windows

hosted

Linux
Unix
Windows

Linux

Data scheme

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

schema-free

Typing

predefined data types such as float or date

yes

yes, details here

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

yes

All search fields are automatically indexed

yes

SQL

Support of SQL

SQL-like query language

yes

via plugins

SQL-like query language (GQL)

APIs and other access methods

Java API
RESTful HTTP/JSON API

Filemaker WebDirect
JDBC
ODBC

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

C++ API
Java API

Supported programming languages

.Net
Groovy
Community Contributed Clients
Java
JavaScript
Perl
PHP
Python
Ruby

PHP

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

.Net
C
C++
Clojure
Go
Haskell
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Nim
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Rust
Swift
Tcl

C
C++
Go
Java
Perl
Python
Ruby

Server-side scripts

Stored procedures

yes

using Google App Engine

Triggers

yes

by using the 'percolation' feature

yes

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication, warm standby

since Version 14

Multi-source replication using Paxos

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

ES-Hadoop Connector

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

yes

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.

Memcached and Redis integration

yes

User concepts

Access control

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

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

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.