DBMS > BigObject vs. CouchDB vs. Ehcache vs. STSdb

System Properties Comparison BigObject vs. CouchDB vs. Ehcache vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Analytic DBMS for real-time computations and queries

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store

Key-value store

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	0.10
Rank	#357	Overall
	#51	Key-value stores

Website

bigobject.io

couchdb.apache.org

www.ehcache.org

github.com/STSSoft/STSdb4

Technical documentation

docs.bigobject.io

docs.couchdb.org/en/stable

www.ehcache.org/documentation

Developer

BigObject, Inc.

Apache Software Foundation

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

Terracotta Inc, owned by Software AG

STS Soft SC

Initial release

2015

2005

2009

2011

Current release

3.3.3, December 2023

3.10.0, March 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

free community edition available

Open Source

Apache version 2

Open Source

Apache Version 2; commercial licenses available

Open Source

GPLv2, commercial license available

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

Erlang

Java

Server operating systems

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Android
BSD
Linux
OS X
Solaris
Windows

All OS with a Java VM

Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

via views

SQL

Support of SQL

SQL-like DML and DDL statements

APIs and other access methods

fluentd
ODBC
RESTful HTTP API

RESTful HTTP/JSON API

JCache

.NET Client API

Supported programming languages

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

Java

C#
Java

Server-side scripts

Stored procedures

Lua

View functions in JavaScript

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

improved architecture with release 2.0

Sharding

by using Terracotta Server

none

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication
Source-replica replication

yes

by using Terracotta Server

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency

Tunable Consistency (Strong, Eventual, Weak)

Foreign keys

Referential integrity

yes

automatically between fact table and dimension tables

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

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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

User concepts

Access control

Access rights for users can be defined per database

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

DB-Engines blog posts

Couchbase climbs up the DB-Engines Ranking, increasing its popularity by 10% every month
2 June 2014, Matthias Gelbmann

show all

Recent citations in the news

How to Automate A Blog Post App Deployment With GitHub Actions, Node.js, CouchDB, and Aptible
4 December 2023, hackernoon.com

HNS IoT Botnet Evolves, Goes Cross-Platform
2 December 2023, Dark Reading

How to install the CouchDB NoSQL database on Debian Server 11
16 June 2022, TechRepublic

IBM Cloudant pulls plan to fund new foundational layer for CouchDB
15 March 2022, The Register

CouchDB 3.0 ends admin party era • DEVCLASS
27 February 2020, DevClass

provided by Google News

Ehcache 2.0: Write-Behind Caching and JTA Support
11 May 2010, InfoQ.com

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Hazelcast signs Java speed king to its in-memory data-grid crew
21 January 2014, The Register

Scaling Australia's Most Popular Online News Sites with Ehcache
6 December 2010, InfoQ.com

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

provided by Google News

Share this page