DBMS > FileMaker vs. MySQL vs. PostGIS vs. Spark SQL vs. Teradata Aster

System Properties Comparison FileMaker vs. MySQL vs. PostGIS vs. Spark SQL vs. Teradata Aster

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed 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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Platform for big data analytics on multistructured data sources and types

Primary database model

Relational DBMS

Key/Value like access via memcached API

Spatial DBMS

Relational 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	18.96
Rank	#33	Overall
	#20	Relational DBMS

Website

www.claris.com/filemaker

www.mysql.com

postgis.net

spark.apache.org/sql

Technical documentation

www.claris.com/resources/documentation

dev.mysql.com/doc

postgis.net/documentation

spark.apache.org/docs/latest/sql-programming-guide.html

Developer

Claris

a subsidiary of Apple

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

Teradata

Initial release

1983

1995

2005

2014

2005

Current release

19.4.1, November 2021

8.4.0, April 2024

3.4.2, February 2024

3.5.0 ( 2.13), September 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

Apache 2.0

commercial

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

Scala

Server operating systems

iOS

client part only
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Linux
OS X
Windows

Linux

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

yes

via plugins

yes

with proprietary extensions

yes

SQL-like DML and DDL statements

yes

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

JDBC
ODBC

ADO.NET
JDBC
ODBC
OLE DB

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

Java
Python
R
Scala

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

yes

proprietary syntax

user defined functions

R packages

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

yes, utilizing Spark Core

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

none

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

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

fine grained access rights according to SQL-standard

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.