DBMS > CouchDB vs. Kingbase vs. RDF4J vs. SiteWhere vs. Snowflake

System Properties Comparison CouchDB vs. Kingbase vs. RDF4J vs. SiteWhere vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

An enterprise-class RDBMS compatible with PostgreSQL and Oracle and widely used in China.

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

M2M integration platform for persisting/querying time series data

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

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

Document store
Spatial DBMS

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

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	0.50
Rank	#257	Overall
	#119	Relational DBMS

Score	0.74
Rank	#222	Overall
	#9	RDF stores

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

couchdb.apache.org

www.kingbase.com.cn

rdf4j.org

github.com/sitewhere/sitewhere

www.snowflake.com

Technical documentation

docs.couchdb.org/en/stable

rdf4j.org/documentation

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

BeiJing KINGBASE Information technologies inc.

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

SiteWhere

Snowflake Computing Inc.

Initial release

2005

1999

2004

2010

2014

Current release

3.3.3, December 2023

V8.0, August 2021

License

Commercial or Open Source

Open Source

Apache version 2

commercial

Open Source

Eclipse Distribution License (EDL), v1.0.

Open Source

Common Public Attribution License Version 1.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

Erlang

C and Java

Java

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

Linux
Windows

Linux
OS X
Unix
Windows

Linux
OS X
Windows

hosted

Data scheme

schema-free

yes

RDF Schemas

predefined scheme

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

via views

yes

SQL

Support of SQL

Standard with numerous extensions

yes

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET
gokb
JDBC
kdbndp
ODBC
PDI
PDO
Pro*C
psycopg2
QT

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

.Net
C
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Java
PHP
Python

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions in JavaScript

user defined functions

yes

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

horizontal partitioning (by range, list and hash) and vertical partitioning

none

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

none

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a single document possible

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

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.

User concepts

Access control

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

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.