DBMS > FileMaker vs. Graph Engine vs. mSQL vs. MySQL vs. OrigoDB

System Properties Comparison FileMaker vs. Graph Engine vs. mSQL vs. MySQL vs. OrigoDB

Editorial information provided by DB-Engines

Name

Description

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

A distributed in-memory data processing engine, underpinned by a strongly-typed RAM store and a general distributed computation engine

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used open source RDBMS

A fully ACID in-memory object graph database

Primary database model

Relational DBMS

Graph DBMS
Key-value store

Relational DBMS

Key/Value like access via memcached API

Document store
Object oriented DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	45.20
Rank	#20	Overall
	#14	Relational DBMS

Score	0.56
Rank	#241	Overall
	#21	Graph DBMS
	#34	Key-value stores

Score	1.26
Rank	#163	Overall
	#74	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#385	Overall
	#54	Document stores
	#21	Object oriented DBMS

Website

www.claris.com/filemaker

www.graphengine.io

hughestech.com.au/products/msql

www.mysql.com

origodb.com

Technical documentation

www.claris.com/resources/documentation

www.graphengine.io/docs/manual

dev.mysql.com/doc

origodb.com/docs

Developer

Claris

a subsidiary of Apple

Microsoft

Hughes Technologies

Oracle

since 2010, originally MySQL AB, then Sun

Robert Friberg et al

Initial release

1983

2010

1994

1995

2009

under the name LiveDB

Current release

19.4.1, November 2021

4.4, October 2021

9.0.0, July 2024

License

Commercial or Open Source

commercial

Open Source

MIT License

commercial

free licenses can be provided

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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

.NET and C

C and C++

Server operating systems

iOS

client part only
Linux
OS X
Windows

.NET

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

User defined using .NET types and collections

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

can be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

yes

via plugins

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

yes

with proprietary extensions

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

RESTful HTTP API

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP API
LINQ

Supported programming languages

PHP

C#
C++
F#
Visual Basic

C
C++
Delphi
Java
Perl
PHP
Tcl

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

.Net

Server-side scripts

Stored procedures

yes

proprietary syntax

yes

Triggers

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

none

Multi-source replication
Source-replica replication

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

depending on model

Transaction concepts

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

ACID

not for MyISAM storage engine

ACID

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

optional: either by committing a write-ahead log (WAL) to the local persistent storage or by dumping the memory to a persistent storage

yes

Write ahead log

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

Users with fine-grained authorization concept

no user groups or roles

Role based authorization

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.