DBMS > FatDB vs. FileMaker vs. GeoMesa vs. Oracle NoSQL

System Properties Comparison FatDB vs. FileMaker vs. GeoMesa vs. Oracle NoSQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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.

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

Primary database model

Document store
Key-value store

Relational DBMS

Spatial DBMS

Document store
Key-value store
Relational DBMS

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	3.07
Rank	#86	Overall
	#15	Document stores
	#11	Key-value stores
	#47	Relational DBMS

Website

www.claris.com/filemaker

www.geomesa.org

www.oracle.com/database/nosql/technologies/nosql

Technical documentation

www.claris.com/resources/documentation

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

docs.oracle.com/en/database/other-databases/nosql-database/index.html

Developer

FatCloud

Claris

a subsidiary of Apple

CCRi and others

Oracle

Initial release

2012

1983

2014

2011

Current release

19.4.1, November 2021

5.0.1, July 2024

24.1, May 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

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

Java

Server operating systems

Windows

iOS

client part only
Linux
OS X
Windows

Linux
Solaris SPARC/x86

Data scheme

schema-free

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Typing

predefined data types such as float or date

yes

optional

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

SQL

Support of SQL

Via inetgration in SQL Server

yes

via plugins

SQL-like DML and DDL statements

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Filemaker WebDirect
JDBC
ODBC

RESTful HTTP API

Supported programming languages

PHP

C
C#
Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

via applications

yes

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication, warm standby

since Version 14

depending on storage layer

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on storage layer

Eventual Consistency
Immediate Consistency

depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

configurable

ACID within a storage node (=shard)

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

off heap cache

User concepts

Access control

Can implement custom security layer via applications

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

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Efficiency leap: Migration from old FileMaker software to gFM-Business increases company performance
19 September 2024, openPR

Problemista - Features
1 March 2024, Reverse Shot

Tilda Swinton Wasn’t Prepared for ‘Problemista’ Horror Stories from Audiences Who Recognize Her Toxic Art World Character
1 March 2024, IndieWire

Apple subsidiary FileMaker returns to its original name from the ’80s
6 August 2019, The Verge

Claris’s Plans for FileMaker Bode Well for Individual Users
23 August 2022, TidBITS

provided by Google News

OpenWorld 2013: Oracle NoSQL Database On the Rise?
13 December 2023, Channel Futures

Cloud database comparison: AWS, Microsoft, Google and Oracle
24 July 2024, TechTarget

Top 8 Best NoSQL Databases in 2024
9 September 2024, AIM

Explore Oracle Database Solutions for Maximum Efficiency
4 September 2018, Oracle

NoSQL Rebels Aim Missile at Larry Ellison's Yacht
20 July 2012, WIRED

provided by Google News

Share this page