DBMS > Blueflood vs. PostGIS vs. Snowflake vs. Spark SQL vs. Stardog

System Properties Comparison Blueflood vs. PostGIS vs. Snowflake vs. Spark SQL vs. Stardog

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

Spatial extension of PostgreSQL

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

Spark SQL is a component on top of 'Spark Core' for structured data processing

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

Primary database model

Secondary database models

Relational DBMS

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

Score	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	21.72
Rank	#29	Overall
	#1	Spatial DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	2.07
Rank	#122	Overall
	#11	Graph DBMS
	#6	RDF stores

Website

Technical documentation

github.com/rax-maas/blueflood/wiki

postgis.net/documentation

docs.snowflake.net/manuals/index.html

spark.apache.org/docs/latest/sql-programming-guide.html

docs.stardog.com

Developer

Rackspace

Snowflake Computing Inc.

Apache Software Foundation

Stardog-Union

Initial release

2013

2005

2014

2010

Current release

3.4.2, February 2024

3.5.0 ( 2.13), September 2023

7.3.0, May 2020

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL v2.0

commercial

Open Source

Apache 2.0

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

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

Scala

Java

Server operating systems

Linux
OS X

hosted

Linux
OS X
Windows

Linux
macOS
Windows

Data scheme

predefined scheme

yes

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

yes

schema-free and OWL/RDFS-schema support

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

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

yes

SQL-like DML and DDL statements

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

HTTP REST

CLI Client
JDBC
ODBC

JDBC
ODBC

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

JavaScript (Node.js)
Python

Java
Python
R
Scala

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

similar concept for controling cloud resources

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

yes

based on PostgreSQL

yes

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

yes

based on PostgreSQL

yes

none

Multi-source replication in HA-Cluster

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Immediate Consistency in HA-Cluster

Foreign keys

Referential integrity

yes

relationships in graphs

Transaction concepts

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

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.

yes

User concepts

Access control

yes

based on PostgreSQL

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

Access rights for users and roles

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.