DBMS > RavenDB vs. ReductStore vs. SiteWhere vs. TimesTen

System Properties Comparison RavenDB vs. ReductStore vs. SiteWhere vs. TimesTen

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Open Source Operational and Transactional Enterprise NoSQL Document Database

Designed to manage unstructured time-series data efficiently, providing unique features such as storing time-stamped blobs with labels, customizable data retention policies, and a straightforward FIFO quota system.

M2M integration platform for persisting/querying time series data

In-Memory RDBMS compatible to Oracle

Primary database model

Document store

Time Series DBMS

Relational DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	0.00
Rank	#383	Overall
	#41	Time Series DBMS

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	1.31
Rank	#163	Overall
	#74	Relational DBMS

Website

ravendb.net

github.com/reductstore
www.reduct.store

github.com/sitewhere/sitewhere

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

ravendb.net/docs

www.reduct.store/docs

sitewhere1.sitewhere.io/index.html

docs.oracle.com/database/timesten-18.1

Developer

Hibernating Rhinos

ReductStore LLC

SiteWhere

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2010

2023

2010

1998

Current release

5.4, July 2022

1.9, March 2024

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

AGPL version 3, commercial license available

Open Source

Business Source License 1.1

Open Source

Common Public Attribution License Version 1.0

commercial

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++, Rust

Java

Server operating systems

Linux
macOS
Raspberry Pi
Windows

Docker
Linux
macOS
Windows

Linux
OS X
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

predefined scheme

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.

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language (RQL)

yes

APIs and other access methods

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

HTTP API

HTTP REST

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

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

C++
JavaScript (Node.js)
Python
Rust

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

yes

PL/SQL

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on HBase

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

based on HBase

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

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

Immediate Consistency or Eventual Consistency depending on configuration

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

by means of logfiles and checkpoints

In-memory capabilities

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

yes

User concepts

Access control

Authorization levels configured per client per database

Users with fine-grained authorization concept

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

RavenDB Welcomes David Baruc as Chief Revenue Officer: Seasoned Tech Leader to Drive Global Sales and ...
13 June 2023, PR Newswire

Install the NoSQL RavenDB Data System
14 May 2021, The New Stack

Oren Eini on RavenDB, Including Consistency Guarantees and C# as the Implementation Language
23 May 2022, InfoQ.com

RavenDB Adds Graph Queries
15 May 2019, Datanami

How I Created a RavenDB Python Client
23 September 2016, Visual Studio Magazine

provided by Google News

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

Ten Popular IoT Platforms You Should be Aware of
27 March 2023, Open Source For You

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Oracle starts peddling Exalytics in-memory appliance
12 March 2012, The Register

provided by Google News

Share this page