DBMS > Oracle NoSQL vs. Realm vs. Snowflake vs. TempoIQ vs. Yanza

System Properties Comparison Oracle NoSQL vs. Realm vs. Snowflake vs. TempoIQ vs. Yanza

Editorial information provided by DB-Engines

Name

TempoIQ seems to be decommissioned. It will be removed from the DB-Engines ranking.

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

Description

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

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

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Time Series DBMS for IoT Applications

Primary database model

Document store
Key-value store
Relational DBMS

Document store

Relational DBMS

Time Series DBMS

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

Score	3.05
Rank	#97	Overall
	#17	Document stores
	#16	Key-value stores
	#50	Relational DBMS

Score	7.41
Rank	#52	Overall
	#8	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.oracle.com/database/nosql/technologies/nosql

realm.io

www.snowflake.com

tempoiq.com (offline)

yanza.com

Technical documentation

docs.oracle.com/en/database/other-databases/nosql-database/index.html

realm.io/docs

docs.snowflake.net/manuals/index.html

Developer

Oracle

Realm, acquired by MongoDB in May 2019

Snowflake Computing Inc.

TempoIQ

Yanza

Initial release

2011

2014

2012

2015

Current release

24.1, May 2024

License

Commercial or Open Source

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

commercial

free version available

Cloud-based only

Only available as a cloud service

yes

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

Server operating systems

Linux
Solaris SPARC/x86

Android
Backend: server-less
iOS
Windows

hosted

Windows

Data scheme

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

yes

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

schema-free

Typing

predefined data types such as float or date

optional

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

SQL-like DML and DDL statements

yes

APIs and other access methods

RESTful HTTP API

CLI Client
JDBC
ODBC

HTTP API

Supported programming languages

C
C#
Go
Java
JavaScript (Node.js)
Python

.Net
Java

with Android only
Objective-C
React Native
Swift

JavaScript (Node.js)
Python

C#
Java
JavaScript

Node.js
Python
Ruby

any language that supports HTTP calls

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

yes

Realtime Alerts

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

none

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

configurable

ACID within a storage node (=shard)

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

off heap cache

yes

In-Memory realm

User concepts

Access control

Access rights for users and roles

yes

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

simple authentication-based access control

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.