DBMS > Databricks vs. FileMaker vs. Microsoft Azure Cosmos DB vs. PostGIS

System Properties Comparison Databricks vs. FileMaker vs. Microsoft Azure Cosmos DB vs. PostGIS

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

The Databricks Lakehouse Platform combines elements of data lakes and data warehouses to provide a unified view onto structured and unstructured data. It is based on Apache Spark.

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

Globally distributed, horizontally scalable, multi-model database service

Spatial extension of PostgreSQL

Primary database model

Document store
Relational DBMS

Relational DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Spatial DBMS

Secondary database models

Spatial DBMS

Relational DBMS

DB-Engines Ranking measures the popularity of database management systems
Trend Chart

Score	78.61
Rank	#15	Overall
	#2	Document stores
	#10	Relational DBMS

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	29.04
Rank	#27	Overall
	#4	Document stores
	#2	Graph DBMS
	#3	Key-value stores
	#3	Wide column stores

Score	22.69
Rank	#29	Overall
	#1	Spatial DBMS

Website

www.databricks.com

www.claris.com/filemaker

azure.microsoft.com/services/cosmos-db

postgis.net

Technical documentation

docs.databricks.com

www.claris.com/resources/documentation

learn.microsoft.com/azure/cosmos-db

postgis.net/documentation

Developer

Databricks

Claris

a subsidiary of Apple

Microsoft

Initial release

2013

1983

2014

2005

Current release

19.4.1, November 2021

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

GPL v2.0

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.

Implementation language

Server operating systems

hosted

iOS

client part only
Linux
OS X
Windows

hosted

Data scheme

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

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

JSON types

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

All properties auto-indexed by default

yes

SQL

Support of SQL

with Databricks SQL

yes

via plugins

SQL-like query language

yes

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

Filemaker WebDirect
JDBC
ODBC

DocumentDB API
Graph API (Gremlin)
MongoDB API
RESTful HTTP API
Table API

Supported programming languages

Python
R
Scala

PHP

.Net
C#
Java
JavaScript
JavaScript (Node.js)
MongoDB client drivers written for various programming languages
Python

Server-side scripts

Stored procedures

user defined functions and aggregates

yes

JavaScript

user defined functions

Triggers

yes

JavaScript

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Implicit feature of the cloud service

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication, warm standby

since Version 14

yes

Implicit feature of the cloud service

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Integration with Hadoop/HDInsight on Azure*

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Consistent Prefix
Eventual Consistency
Immediate Consistency

Consistency level configurable on request level
Session Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Multi-item ACID transactions with snapshot isolation within a partition

ACID

Concurrency

Support for concurrent manipulation of data

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.

User concepts

Access control

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

Access rights can be defined down to the item level

yes

based on PostgreSQL

More information provided by the system vendor

Specific characteristics

Supported database models : In addition to the Document store and Relational DBMS...
» more

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.