DBMS > FileMaker vs. Microsoft Azure Data Explorer vs. MySQL vs. OrigoDB vs. SAP SQL Anywhere

System Properties Comparison FileMaker vs. Microsoft Azure Data Explorer vs. MySQL vs. OrigoDB vs. SAP SQL Anywhere

Editorial information provided by DB-Engines

Name

Description

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

Fully managed big data interactive analytics platform

Widely used open source RDBMS

A fully ACID in-memory object graph database

RDBMS database and synchronization technologies for server, desktop, remote office, and mobile environments

Primary database model

Relational DBMS

column oriented

Relational DBMS

Key/Value like access via memcached API

Document store
Object oriented DBMS

Relational DBMS

Secondary database models

Document store

If a column is of type dynamic docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types/dynamic then it's possible to add arbitrary JSON documents in this cell
Event Store

this is the general usage pattern at Microsoft. Billing, Logs, Telemetry events are stored in ADX and the state of an individual entity is defined by the arg_max(timestamps)
Spatial DBMS
Search engine

support for complex search expressions docs.microsoft.com/en-us/azure/kusto/query/parseoperator FTS, Geospatial docs.microsoft.com/en-us/azure/kusto/query/geo-point-to-geohash-function distributed search -> ADX acts as a distributed search engine
Time Series DBMS

see docs.microsoft.com/en-us/azure/data-explorer/time-series-analysis

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.38
Rank	#77	Overall
	#41	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Score	4.25
Rank	#79	Overall
	#43	Relational DBMS

Website

www.claris.com/filemaker

azure.microsoft.com/services/data-explorer

www.mysql.com

origodb.com

www.sap.com/products/technology-platform/sql-anywhere.html

Technical documentation

www.claris.com/resources/documentation

docs.microsoft.com/en-us/azure/data-explorer

dev.mysql.com/doc

origodb.com/docs

help.sap.com/docs/SAP_SQL_Anywhere

Developer

Claris

a subsidiary of Apple

Microsoft

Oracle

since 2010, originally MySQL AB, then Sun

Robert Friberg et al

SAP

formerly Sybase

Initial release

1983

2019

1995

2009

under the name LiveDB

1992

Current release

19.4.1, November 2021

cloud service with continuous releases

8.4.0, April 2024

17, July 2015

License

Commercial or Open Source

commercial

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

Open Source

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

Server operating systems

iOS

client part only
Linux
OS X
Windows

hosted

FreeBSD
Linux
OS X
Solaris
Windows

Linux
Windows

AIX
HP-UX
Linux
OS X
Solaris
Windows

Data scheme

yes

Fixed schema with schema-less datatypes (dynamic)

yes

Typing

predefined data types such as float or date

yes

bool, datetime, dynamic, guid, int, long, real, string, timespan, double: docs.microsoft.com/en-us/azure/kusto/query/scalar-data-types

yes

User defined using .NET types and collections

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

can be achieved using .NET

yes

Secondary indexes

yes

all fields are automatically indexed

yes

SQL

Support of SQL

yes

via plugins

Kusto Query Language (KQL), SQL subset

yes

with proprietary extensions

yes

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

Microsoft SQL Server communication protocol (MS-TDS)
RESTful HTTP API

ADO.NET
JDBC
ODBC
Proprietary native API

.NET Client API
HTTP API
LINQ

ADO.NET
HTTP API
JDBC
ODBC

Supported programming languages

PHP

.Net
Go
Java
JavaScript (Node.js)
PowerShell
Python
R

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

.Net

C
C#
C++
Delphi
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes

Yes, possible languages: KQL, Python, R

yes

proprietary syntax

yes

yes, in C/C++, Java, .Net or Perl

Triggers

yes

see docs.microsoft.com/en-us/azure/kusto/management/updatepolicy

yes

Domain Events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

horizontal partitioning

client side managed; servers are not synchronized

none

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

yes

Implicit feature of the cloud service. Replication either local, cross-facility or geo-redundant.

Multi-source replication
Source-replica replication

Source-replica replication

Database mirroring

MapReduce

Offers an API for user-defined Map/Reduce methods

Spark connector (open source): github.com/Azure/azure-kusto-spark

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

depending on model

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

Write ahead log

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

Azure Active Directory Authentication

Users with fine-grained authorization concept

no user groups or roles

Role based authorization

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.