DBMS > FileMaker vs. Newts vs. RavenDB vs. Snowflake vs. Transwarp KunDB

System Properties Comparison FileMaker vs. Newts vs. RavenDB vs. Snowflake vs. Transwarp KunDB

Editorial information provided by DB-Engines

Name

Description

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

Time Series DBMS based on Cassandra

Open Source Operational and Transactional Enterprise NoSQL Document Database

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

OLTP DBMS based on a distributed architecture and highly compatible with MySQL and Oracle

Primary database model

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	48.20
Rank	#20	Overall
	#14	Relational DBMS

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	0.10
Rank	#344	Overall
	#151	Relational DBMS

Website

www.claris.com/filemaker

opennms.github.io/newts

ravendb.net

www.snowflake.com

www.transwarp.cn/en/product/kundb

Technical documentation

www.claris.com/resources/documentation

github.com/OpenNMS/newts/wiki

ravendb.net/docs

docs.snowflake.net/manuals/index.html

Developer

Claris

a subsidiary of Apple

OpenNMS Group

Hibernating Rhinos

Snowflake Computing Inc.

Transwarp

Initial release

1983

2014

2010

2014

Current release

19.4.1, November 2021

5.4, July 2022

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

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

Java

Server operating systems

iOS

client part only
Linux
OS X
Windows

Linux
OS X
Windows

Linux
macOS
Raspberry Pi
Windows

hosted

Data scheme

yes

schema-free

yes

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

yes

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

HTTP REST
Java API

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

CLI Client
JDBC
ODBC

Supported programming languages

PHP

Java

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

user defined functions

yes

Triggers

yes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on Cassandra

Sharding

yes

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication, warm standby

since Version 14

selectable replication factor

based on Cassandra

Multi-source replication

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

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

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

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

yes

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.