DBMS > FatDB vs. MarkLogic vs. RDF4J vs. Snowflake

System Properties Comparison FatDB vs. MarkLogic vs. RDF4J vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Operational and transactional Enterprise NoSQL database

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

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

Primary database model

Document store
Key-value store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

RDF store

Relational DBMS

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

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.marklogic.com

rdf4j.org

www.snowflake.com

Technical documentation

docs.marklogic.com

rdf4j.org/documentation

docs.snowflake.net/manuals/index.html

Developer

FatCloud

MarkLogic Corp.

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Snowflake Computing Inc.

Initial release

2012

2001

2004

2014

Current release

11.0, December 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Eclipse Distribution License (EDL), v1.0.

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

Java

Server operating systems

Windows

Linux
OS X
Windows

Linux
OS X
Unix
Windows

hosted

Data scheme

schema-free

Schema can be enforced

yes

RDF Schemas

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

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

SQL92

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

CLI Client
JDBC
ODBC

Supported programming languages

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

Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes

via applications

yes

via XQuery or JavaScript

yes

user defined functions

Triggers

yes

via applications

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

can act as a resource manager in an XA/JTA transaction

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes, with Range Indexes

User concepts

Access control

Can implement custom security layer via applications

Role-based access control at the document and subdocument levels

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.