DBMS > FeatureBase vs. FileMaker vs. OpenQM vs. searchxml vs. Snowflake

System Properties Comparison FeatureBase vs. FileMaker vs. OpenQM vs. searchxml vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Real-time database platform that powers real-time analytics and machine learning applications by simultaneously executing low-latency, high-throughput, and highly concurrent workloads.

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

QpenQM is a high-performance, self-tuning, multi-value DBMS

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

Multivalue DBMS

Native XML DBMS
Search engine

Relational DBMS

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

Score	0.22
Rank	#309	Overall
	#139	Relational DBMS

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	0.27
Rank	#298	Overall
	#10	Multivalue DBMS

Score	0.00
Rank	#383	Overall
	#7	Native XML DBMS
	#25	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

www.featurebase.com

www.claris.com/filemaker

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-open-qm

www.searchxml.net/category/products

www.snowflake.com

Technical documentation

docs.featurebase.com

www.claris.com/resources/documentation

www.searchxml.net/support/handouts

docs.snowflake.net/manuals/index.html

Developer

Molecula and Pilosa Open Source Contributors

Claris

a subsidiary of Apple

Rocket Software, originally Martin Phillips

informationpartners gmbh

Snowflake Computing Inc.

Initial release

2017

1983

1993

2015

2014

Current release

2022, May 2022

19.4.1, November 2021

3.4-12

1.0

License

Commercial or Open Source

commercial

Open Source

GPLv2, extended 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

Linux
macOS

iOS

client part only
Linux
OS X
Windows

AIX
FreeBSD
Linux
macOS
Raspberry Pi
Solaris
Windows

Windows

hosted

Data scheme

yes

with some exceptions

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

SQL queries

yes

via plugins

yes

APIs and other access methods

gRPC
JDBC
Kafka Connector
ODBC

Filemaker WebDirect
JDBC
ODBC

RESTful HTTP API
WebDAV
XQuery
XSLT

CLI Client
JDBC
ODBC

Supported programming languages

Java
Python

PHP

.Net
Basic
C
Java
Objective C
PHP
Python

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

Sharding

none

yes

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication, warm standby

since Version 14

yes

sychronisation to multiple collections

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

multiple readers, single writer

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes, using Linux fsync

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

Access rights can be defined down to the item level

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.