DBMS > FileMaker vs. MySQL vs. PostGIS vs. ToroDB vs. VictoriaMetrics

System Properties Comparison FileMaker vs. MySQL vs. PostGIS vs. ToroDB vs. VictoriaMetrics

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

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

Widely used open source RDBMS

Spatial extension of PostgreSQL

A MongoDB-compatible JSON document store, built on top of PostgreSQL

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Document store

Time Series 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	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

www.claris.com/filemaker

www.mysql.com

postgis.net

github.com/torodb/server

victoriametrics.com

Technical documentation

www.claris.com/resources/documentation

dev.mysql.com/doc

postgis.net/documentation

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Claris

a subsidiary of Apple

Oracle

since 2010, originally MySQL AB, then Sun

8Kdata

VictoriaMetrics

Initial release

1983

1995

2005

2016

2018

Current release

19.4.1, November 2021

8.4.0, April 2024

3.4.2, February 2024

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

GPL v2.0

Open Source

AGPL-V3

Open Source

Apache Version 2.0

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.

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++

Java

Server operating systems

iOS

client part only
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

All OS with a Java 7 VM

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, boolean, date, object_id

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

yes

with proprietary extensions

yes

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

PHP

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

proprietary syntax

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

yes

based on PostgreSQL

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

Multi-source replication
Source-replica replication

yes

based on PostgreSQL

Source-replica replication

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

yes

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

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

yes

based on PostgreSQL

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.