DBMS > Google BigQuery vs. NCache vs. RavenDB vs. VoltDB

System Properties Comparison Google BigQuery vs. NCache vs. RavenDB vs. VoltDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

Open-Source and Enterprise in-memory Key-Value Store

Open Source Operational and Transactional Enterprise NoSQL Document Database

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Secondary database models

Document store
Search engine

Using distributed Lucene

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.94
Rank	#195	Overall
	#29	Key-value stores

Score	2.92
Rank	#101	Overall
	#18	Document stores

Score	1.44
Rank	#158	Overall
	#73	Relational DBMS

Website

cloud.google.com/bigquery

www.alachisoft.com/ncache

ravendb.net

www.voltdb.com

Technical documentation

cloud.google.com/bigquery/docs

www.alachisoft.com/resources/docs

ravendb.net/docs

docs.voltdb.com

Developer

Google

Alachisoft

Hibernating Rhinos

VoltDB Inc.

Initial release

2010

2005

2010

Current release

5.3.3, April 2024

5.4, July 2022

11.3, April 2022

License

Commercial or Open Source

commercial

Open Source

Enterprise Edition available

Open Source

AGPL version 3, commercial license available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

C#, .NET, .NET Core, Java

Java, C++

Server operating systems

hosted

Linux
Windows

Linux
macOS
Raspberry Pi
Windows

Linux
OS X

for development

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

partial

Supported data types are Lists, Queues, Hashsets, Dictionary and Counter

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

yes

SQL-like query syntax and LINQ for searching the cache. Cache Synchronization with SQL Server using SQL dependency.

SQL-like query language (RQL)

yes

only a subset of SQL 99

APIs and other access methods

RESTful HTTP/JSON API

IDistributedCache
JCache
LINQ
Proprietary native API

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

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

.Net
.Net Core
C#
Java
JavaScript (Node.js)
Python
Scala

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

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

support for stored procedures with SQL-Server CLR

yes

Java

Triggers

yes

Notifications

yes

Partitioning methods

Methods for storing different data on different nodes

none

yes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes, with selectable consistency level

Multi-source replication

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

Immediate Consistency

Eventual Consistency
Immediate Consistency
Strong Eventual Consistency over WAN with Conflict Resolution using Bridge Topology

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.

Foreign keys

Referential integrity

FOREIGN KEY constraints are not supported

Transaction concepts

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

Since BigQuery is designed for querying data

optimistic locking and pessimistic locking

ACID, Cluster-wide transaction available

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

Authentication to access the cache via Active Directory/LDAP (possible roles: user, administrator)

Authorization levels configured per client per database

Users and roles with access to stored procedures

More information provided by the system vendor

Specific characteristics

NCache has been the market leader in .NET Distributed Caching since 2005 . NCache...
» more

Competitive advantages

NCache is 100% .NET/ .NET Core based which fully supports ASP.NET Core Sessions ,...
» more

Typical application scenarios

NCache enables industries like retail, finance, banking IoT, travel, ecommerce, healthcare...
» more

Key customers

Bank of America, Citi, Natures Way, Charter Spectrum, Barclays, Henry Schein, GBM,...
» more

Market metrics

Market Leader in .NET Distributed Caching since 2005.
» more

Licensing and pricing models

NCache Open Source is free on an as-is basis without any support. NCache Enterprise...
» more

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.