DBMS > Couchbase vs. Ehcache vs. Microsoft Access vs. Sphinx vs. TimesTen

System Properties Comparison Couchbase vs. Ehcache vs. Microsoft Access vs. Sphinx vs. TimesTen

Editorial information provided by DB-Engines

Name

Description

A distributed document store with integrated cache, a powerful search engine, in-built operational and analytical capabilities, and an embedded mobile database

A widely adopted Java cache with tiered storage options

Microsoft Access combines a backend RDBMS (JET / ACE Engine) with a GUI frontend for data manipulation and queries.

The Access frontend is often used for accessing other datasources (DBMS, Excel, etc.)

Open source search engine for searching in data from different sources, e.g. relational databases

In-Memory RDBMS compatible to Oracle

Primary database model

Secondary database models

Key-value store

originating from the former Membase product and supporting the Memcached protocol
Spatial DBMS

using the Geocouch extension
Search engine
Time Series DBMS
Vector DBMS

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

Score	16.59
Rank	#36	Overall
	#5	Document stores

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

Score	101.16
Rank	#11	Overall
	#8	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	1.36
Rank	#161	Overall
	#75	Relational DBMS

Website

www.couchbase.com

www.ehcache.org

www.microsoft.com/en-us/microsoft-365/access

sphinxsearch.com

www.oracle.com/database/technologies/related/timesten.html

Technical documentation

docs.couchbase.com

www.ehcache.org/documentation

developer.microsoft.com/en-us/access

sphinxsearch.com/docs

docs.oracle.com/database/timesten-18.1

Developer

Couchbase, Inc.

Terracotta Inc, owned by Software AG

Microsoft

Sphinx Technologies Inc.

Oracle, TimesTen Performance Software, HP

originally founded in HP Labs it was acquired by Oracle in 2005

Initial release

2011

2009

1992

2001

1998

Current release

Server: 7.2, June 2023; Mobile: 3.1, March 2022; Couchbase Capella (DBaaS), June 2023

3.10.0, March 2022

1902 (16.0.11328.20222), March 2019

3.5.1, February 2023

11 Release 2 (11.2.2.8.0)

License

Commercial or Open Source

Open Source

Business Source License (BSL 1.1); Commercial licenses also available

Open Source

Apache Version 2; commercial licenses available

commercial

Bundled with Microsoft Office

Open Source

GPL version 2, commercial licence available

commercial

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

C, C++, Go and Erlang

Java

C++

Server operating systems

Linux
OS X
Windows

All OS with a Java VM

Windows

Not a real database server, but making use of DLLs

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

AIX
HP-UX
Linux
OS X
Solaris SPARC/x86
Windows

Data scheme

schema-free

yes

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.

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL++, extends ANSI SQL to JSON for operational, transactional, and analytic use cases

yes

but not compliant to any SQL standard

SQL-like query language (SphinxQL)

yes

APIs and other access methods

CLI Client
HTTP REST
Kafka Connector
Native language bindings for CRUD, Query, Search and Analytics APIs
Spark Connector
Spring Data

JCache

ADO.NET
DAO
ODBC
OLE DB

Proprietary protocol

JDBC
ODBC
ODP.NET
Oracle Call Interface (OCI)

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

Java

C
C#
C++
Delphi
Java (JDBC-ODBC)
VBA
Visual Basic.NET

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C
C++
Java
PL/SQL

Server-side scripts

Stored procedures

Functions and timers in JavaScript and UDFs in Java, Python, SQL++

yes

since Access 2010 using the ACE-engine

PL/SQL

Triggers

yes

via the TAP protocol

yes

Cache Event Listeners

yes

since Access 2010 using the ACE-engine

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

Sharding

by using Terracotta Server

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

yes

by using Terracotta Server

none

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

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Tunable Consistency (Strong, Eventual, Weak)

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

supports JTA and can work as an XA resource

ACID

but no files for transaction logging

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

but no files for transaction logging

yes

The original contents of fields are not stored in the Sphinx index.

yes

by means of logfiles and checkpoints

In-memory capabilities

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

yes

Ephemeral buckets

yes

User concepts

Access control

User and Administrator separation with password-based and LDAP integrated Authentication. Role-base access control.

a simple user-level security was built in till version Access 2003

fine grained access rights according to SQL-standard

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.