DBMS > Apache Drill vs. Atos Standard Common Repository vs. FileMaker vs. MySQL

System Properties Comparison Apache Drill vs. Atos Standard Common Repository vs. FileMaker vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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

Widely used open source RDBMS

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Relational DBMS

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	1.95
Rank	#127	Overall
	#23	Document stores
	#60	Relational DBMS

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

drill.apache.org

atos.net/en/convergence-creators/portfolio/standard-common-repository

www.claris.com/filemaker

www.mysql.com

Technical documentation

drill.apache.org/docs

www.claris.com/resources/documentation

dev.mysql.com/doc

Developer

Apache Software Foundation

Atos Convergence Creators

Claris

a subsidiary of Apple

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2012

2016

1983

1995

Current release

1.20.3, January 2023

1703

19.4.1, November 2021

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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

Java

C and C++

Server operating systems

Linux
OS X
Windows

Linux

iOS

client part only
Linux
OS X
Windows

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

Typing

predefined data types such as float or date

yes

optional

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

SQL SELECT statement is SQL:2003 compliant

yes

via plugins

yes

with proprietary extensions

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

LDAP

Filemaker WebDirect
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

Supported programming languages

C++

All languages with LDAP bindings

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

user defined functions

yes

proprietary syntax

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication, warm standby

since Version 14

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

Atomic execution of specific operations

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

User concepts

Access control

Depending on the underlying data source

LDAP bind authentication

simple rights management via user accounts and connection to external directory services

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.