DBMS > FileMaker vs. Google Cloud Datastore vs. mSQL vs. MySQL vs. SpaceTime

System Properties Comparison FileMaker vs. Google Cloud Datastore vs. mSQL vs. MySQL vs. SpaceTime

Editorial information provided by DB-Engines

Name

Description

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

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

mSQL (Mini SQL) is a simple and lightweight RDBMS

Widely used open source RDBMS

SpaceTime is a spatio-temporal DBMS with a focus on performance.

Primary database model

Relational DBMS

Document store

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#7	Spatial DBMS

Website

www.claris.com/filemaker

cloud.google.com/datastore

hughestech.com.au/products/msql

www.mysql.com

www.mireo.com/spacetime

Technical documentation

www.claris.com/resources/documentation

cloud.google.com/datastore/docs

dev.mysql.com/doc

Developer

Claris

a subsidiary of Apple

Google

Hughes Technologies

Oracle

since 2010, originally MySQL AB, then Sun

Mireo

Initial release

1983

2008

1994

1995

2020

Current release

19.4.1, November 2021

4.4, October 2021

8.3.0, January 2024

License

Commercial or Open Source

commercial

free licenses can be provided

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

commercial

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

C and C++

C++

Server operating systems

iOS

client part only
Linux
OS X
Windows

hosted

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

FreeBSD
Linux
OS X
Solaris
Windows

Linux

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

Secondary indexes

yes

SQL

Support of SQL

yes

via plugins

SQL-like query language (GQL)

A subset of ANSI SQL is implemented

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

yes

with proprietary extensions

A subset of ANSI SQL is implemented

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

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

JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

RESTful HTTP API

Supported programming languages

PHP

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

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

C#
C++
Python

Server-side scripts

Stored procedures

yes

using Google App Engine

yes

proprietary syntax

Triggers

yes

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Fixed-grid hypercubes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

Multi-source replication using Paxos

none

Multi-source replication
Source-replica replication

Real-time block device replication (DRBD)

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

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.

none

Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

ACID

not for MyISAM storage engine

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

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 for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Users with fine-grained authorization concept

no user groups or roles

yes

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.