DBMS > FileMaker vs. GeoMesa vs. Oracle vs. Oracle Berkeley DB

System Properties Comparison FileMaker vs. GeoMesa vs. Oracle vs. Oracle Berkeley DB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

Widely used RDBMS

Widely used in-process key-value store

Primary database model

supports sorted and unsorted key sets
Native XML DBMS

in the Oracle Berkeley DB XML version

Secondary database models

Document store
Graph DBMS

with Oracle Spatial and Graph
RDF store

with Oracle Spatial and Graph
Spatial DBMS

with Oracle Spatial and Graph
Vector DBMS

since Oracle 23

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

Score	45.20
Rank	#20	Overall
	#14	Relational DBMS

Score	0.78
Rank	#214	Overall
	#4	Spatial DBMS

Score	1286.59
Rank	#1	Overall
	#1	Relational DBMS

Score	1.88
Rank	#130	Overall
	#23	Key-value stores
	#3	Native XML DBMS

Website

www.claris.com/filemaker

www.geomesa.org

www.oracle.com/database

www.oracle.com/database/technologies/related/berkeleydb.html

Technical documentation

www.claris.com/resources/documentation

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

docs.oracle.com/en/database

docs.oracle.com/cd/E17076_05/html/index.html

Developer

Claris

a subsidiary of Apple

CCRi and others

Oracle

originally developed by Sleepycat, which was acquired by Oracle

Initial release

1983

2014

1980

1994

Current release

19.4.1, November 2021

5.0.1, July 2024

23c, September 2023

18.1.40, May 2020

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

commercial

restricted free version is available

Open Source

commercial license available

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

Scala

C and C++

C, Java, C++ (depending on the Berkeley DB edition)

Server operating systems

iOS

client part only
Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows
z/OS

AIX
Android
FreeBSD
iOS
Linux
OS X
Solaris
VxWorks
Windows

Data scheme

yes

Schemaless in JSON and XML columns

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

yes

only with the Berkeley DB XML edition

Secondary indexes

yes

SQL

Support of SQL

yes

via plugins

yes

with proprietary extensions

yes

SQL interfaced based on SQLite is available

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

PHP

C
C#
C++
Clojure
Cobol
Delphi
Eiffel
Erlang
Fortran
Groovy
Haskell
Java
JavaScript
Lisp
Objective C
OCaml
Perl
PHP
Python
R
Ruby
Scala
Tcl
Visual Basic

.Net

Figaro is a .Net framework assembly that extends Berkeley DB XML into an embeddable database engine for .NET
others

Third-party libraries to manipulate Berkeley DB files are available for many languages
C
C#
C++
Java
JavaScript (Node.js)

3rd party binding
Perl
Python
Tcl

Server-side scripts

Stored procedures

yes

PL/SQL

also stored procedures in Java possible

Triggers

yes

only for the SQL API

Partitioning methods

Methods for storing different data on different nodes

none

depending on storage layer

Sharding, horizontal partitioning

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

depending on storage layer

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

can be realized in PL/SQL

Consistency concepts

Methods to ensure consistency in a distributed system

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 level can be parameterized

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.

depending on storage layer

yes

Version 12c introduced the new option 'Oracle Database In-Memory'

yes

User concepts

Access control

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

yes

depending on the DBMS used for storage

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.