DBMS > Couchbase vs. Realm vs. STSdb vs. Teradata Aster

System Properties Comparison Couchbase vs. Realm vs. STSdb vs. Teradata Aster

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Teradata Aster has been integrated into other Teradata systems and therefore will be removed from the DB-Engines ranking.

Description

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

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

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Platform for big data analytics on multistructured data sources and types

Primary database model

Document store

Key-value store

Relational DBMS

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	7.41
Rank	#52	Overall
	#8	Document stores

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

Website

www.couchbase.com

realm.io

github.com/STSSoft/STSdb4

Technical documentation

docs.couchbase.com

realm.io/docs

Developer

Couchbase, Inc.

Realm, acquired by MongoDB in May 2019

STS Soft SC

Teradata

Initial release

2011

2014

2011

2005

Current release

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

4.0.8, September 2015

License

Commercial or Open Source

Open Source

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

Open Source

GPLv2, commercial license 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

Server operating systems

Linux
OS X
Windows

Android
Backend: server-less
iOS
Windows

Windows

Linux

Data scheme

schema-free

yes

Flexible Schema (defined schema, partial schema, schema free)

defined schema within the relational store; partial schema or schema free in the Aster File Store

Typing

predefined data types such as float or date

yes

primitive types and user defined types (classes)

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

in Aster File Store

Secondary indexes

yes

SQL

Support of SQL

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

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

.NET Client API

ADO.NET
JDBC
ODBC
OLE DB

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.Net
Java

with Android only
Objective-C
React Native
Swift

C#
Java

C
C#
C++
Java
Python
R

Server-side scripts

Stored procedures

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

runs within the applications so server-side scripts are unnecessary

R packages

Triggers

yes

via the TAP protocol

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

none

yes

Dimension tables are replicated across all nodes in the cluster. The number of replicas for the file store can be configured.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

SQL Map-Reduce Framework

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Immediate Consistency

Immediate Consistency or Eventual Consistency depending on configuration

Foreign keys

Referential integrity

Transaction concepts

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

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

Ephemeral buckets

yes

In-Memory realm

User concepts

Access control

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

yes

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.