DBMS > FileMaker vs. RavenDB vs. searchxml vs. Snowflake

System Properties Comparison FileMaker vs. RavenDB vs. searchxml vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

Open Source Operational and Transactional Enterprise NoSQL Document Database

DBMS for structured and unstructured content wrapped with an application server

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Relational DBMS

Document store

Native XML DBMS
Search engine

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	49.73
Rank	#20	Overall
	#14	Relational DBMS

Score	3.01
Rank	#101	Overall
	#17	Document stores

Score	0.01
Rank	#386	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	123.20
Rank	#9	Overall
	#6	Relational DBMS

Website

www.claris.com/filemaker

ravendb.net

www.searchxml.net/category/products

www.snowflake.com

Technical documentation

www.claris.com/resources/documentation

ravendb.net/docs

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

Developer

Claris

a subsidiary of Apple

Hibernating Rhinos

informationpartners gmbh

Snowflake Computing Inc.

Initial release

1983

2010

2015

2014

Current release

19.4.1, November 2021

5.4, July 2022

1.0

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

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.

Implementation language

C++

Server operating systems

iOS

client part only
Linux
OS X
Windows

Linux
macOS
Raspberry Pi
Windows

Windows

hosted

Data scheme

yes

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

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

Secondary indexes

yes

SQL

Support of SQL

yes

via plugins

SQL-like query language (RQL)

yes

APIs and other access methods

Filemaker WebDirect
JDBC
ODBC

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

Supported programming languages

PHP

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

C++

most other programming languages supported via APIs

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

on the application server

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

Multi-source replication

yes

sychronisation to multiple collections

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID, Cluster-wide transaction available

multiple readers, single writer

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

Authorization levels configured per client per database

Domain, group and role-based access control at the document level and for application services

Users with fine-grained authorization concept, user roles and pluggable authentication

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.