DBMS > CouchDB vs. Ehcache vs. Google Cloud Firestore vs. Machbase Neo vs. Snowflake

System Properties Comparison CouchDB vs. Ehcache vs. Google Cloud Firestore vs. Machbase Neo 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.

A widely adopted Java cache with tiered storage options

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

TimeSeries DBMS for AIoT and BigData

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

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	9.30
Rank	#45	Overall
	#7	Document stores

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.12
Rank	#339	Overall
	#30	Time Series DBMS

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Website

couchdb.apache.org

www.ehcache.org

firebase.google.com/products/firestore

machbase.com

www.snowflake.com

Technical documentation

docs.couchdb.org/en/stable

www.ehcache.org/documentation

firebase.google.com/docs/firestore

machbase.com/dbms

docs.snowflake.net/manuals/index.html

Developer

Apache Software Foundation

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

Terracotta Inc, owned by Software AG

Google

Machbase

Snowflake Computing Inc.

Initial release

2005

2009

2017

2013

2014

Current release

3.3.3, December 2023

3.10.0, March 2022

V8.0, August 2023

License

Commercial or Open Source

Open Source

Apache version 2

Open Source

Apache Version 2; commercial licenses available

commercial

free test version available

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

Java

Server operating systems

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

hosted

Linux
macOS
Windows

hosted

Data scheme

schema-free

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

SQL-like query language

yes

APIs and other access methods

RESTful HTTP/JSON API

JCache

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

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

Java

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

View functions in JavaScript

yes, Firebase Rules & Cloud Functions

user defined functions

Triggers

yes

Cache Event Listeners

yes, with Cloud Functions

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

Sharding

by using Terracotta Server

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

yes

by using Terracotta Server

Multi-source replication

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Tunable Consistency (Strong, Eventual, Weak)

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

yes

supports JTA and can work as an XA resource

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

volatile and lookup table

User concepts

Access control

Access rights for users can be defined per database

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

simple password-based access control

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.