DBMS > Realm vs. SiteWhere vs. Snowflake

System Properties Comparison Realm vs. SiteWhere vs. Snowflake

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

M2M integration platform for persisting/querying time series data

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

Primary database model

Document store

Time Series DBMS

Relational DBMS

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

Score	7.60
Rank	#52	Overall
	#9	Document stores

Score	0.06
Rank	#356	Overall
	#35	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

realm.io

github.com/sitewhere/sitewhere

www.snowflake.com

Technical documentation

realm.io/docs

sitewhere1.sitewhere.io/index.html

docs.snowflake.net/manuals/index.html

Developer

Realm, acquired by MongoDB in May 2019

SiteWhere

Snowflake Computing Inc.

Initial release

2014

2010

2014

License

Commercial or Open Source

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

Java

Server operating systems

Android
Backend: server-less
iOS
Windows

Linux
OS X
Windows

hosted

Data scheme

yes

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

SQL

Support of SQL

yes

APIs and other access methods

HTTP REST

CLI Client
JDBC
ODBC

Supported programming languages

.Net
Java

with Android only
Objective-C
React Native
Swift

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

runs within the applications so server-side scripts are unnecessary

user defined functions

Triggers

yes

Change Listeners

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

based on HBase

yes

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

based on HBase

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

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

In-Memory realm

User concepts

Access control

yes

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.