DBMS > GeoSpock vs. IRONdb vs. Microsoft SQL Server vs. RDF4J vs. Rockset

System Properties Comparison GeoSpock vs. IRONdb vs. Microsoft SQL Server vs. RDF4J vs. Rockset

Editorial information provided by DB-Engines

Name

GeoSpock seems to be discontinued. Therefore it will be excluded from the DB-Engines ranking.

IRONdb seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Spatial and temporal data processing engine for extreme data scale

A distributed Time Series DBMS with a focus on scalability, fault tolerance and operational simplicity

Microsofts flagship relational DBMS

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

A scalable, reliable search and analytics service in the cloud, built on RocksDB

Primary database model

Secondary database models

Time Series DBMS

Document store
Graph DBMS
Spatial DBMS

Relational DBMS
Search engine

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.69
Rank	#230	Overall
	#9	RDF stores

Score	0.79
Rank	#211	Overall
	#35	Document stores

Website

geospock.com

www.circonus.com/solutions/time-series-database/

www.microsoft.com/en-us/sql-server

rdf4j.org

rockset.com

Technical documentation

docs.circonus.com/irondb/category/getting-started

learn.microsoft.com/en-US/sql/sql-server

rdf4j.org/documentation

docs.rockset.com

Developer

GeoSpock

Circonus LLC.

Microsoft

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

Rockset

Initial release

2017

1989

2004

2019

Current release

2.0, September 2019

V0.10.20, January 2018

SQL Server 2022, November 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

Java, Javascript

C and C++

C++

Java

C++

Server operating systems

hosted

Linux

Linux
Windows

Linux
OS X
Unix
Windows

hosted

Data scheme

yes

schema-free

yes

RDF Schemas

schema-free

Typing

predefined data types such as float or date

yes

text, numeric, histograms

yes

dynamic typing

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

ingestion from XML files supported

Secondary indexes

temporal, categorical

yes

all fields are automatically indexed

SQL

Support of SQL

ANSI SQL for query only (using Presto)

SQL-like query language (Circonus Analytics Query Language: CAQL)

yes

Read-only SQL queries, including JOINs

APIs and other access methods

JDBC

HTTP API

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

HTTP REST

Supported programming languages

.Net
C
C++
Clojure
Erlang
Go
Haskell
Java
JavaScript
JavaScript (Node.js)
Lisp
Lua
Perl
PHP
Python
R
Ruby
Rust
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Java
PHP
Python

Go
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

yes, in Lua

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic sharding

Automatic, metric affinity per node

tables can be distributed across several files (horizontal partitioning); sharding through federation

none

Automatic sharding

Replication methods

Methods for redundantly storing data on multiple nodes

configurable replication factor, datacenter aware

yes, but depending on the SQL-Server Edition

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Immediate consistency per node, eventual consistency across nodes

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Isolation support depends on the API used

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

User concepts

Access control

Access rights for users can be defined per table

fine grained access rights according to SQL-standard

Access rights for users and organizations can be defined via Rockset console

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.