DBMS > FileMaker vs. Google Cloud Datastore vs. Graphite vs. MySQL

System Properties Comparison FileMaker vs. Google Cloud Datastore vs. Graphite vs. MySQL

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.

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

Data logging and graphing tool for time series data

The storage layer (fixed size database) is called Whisper

Widely used open source RDBMS

Primary database model

Key/Value like access via memcached API

Secondary database models

Document store
Spatial 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	4.57
Rank	#73	Overall
	#5	Time Series DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

www.claris.com/filemaker

cloud.google.com/datastore

github.com/graphite-project/graphite-web

www.mysql.com

Technical documentation

www.claris.com/resources/documentation

cloud.google.com/datastore/docs

graphite.readthedocs.io

dev.mysql.com/doc

Developer

Claris

a subsidiary of Apple

Google

Chris Davis

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

1983

2008

2006

1995

Current release

19.4.1, November 2021

8.4.0, April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Python

C and C++

Server operating systems

iOS

client part only
Linux
OS X
Windows

hosted

Linux
Unix

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

Numeric data only

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)

yes

with proprietary extensions

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

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

HTTP API
Sockets

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

PHP

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

JavaScript (Node.js)
Python

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

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

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

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

locking

yes

table locks or row locks depending on storage engine

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

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.