DBMS > Couchbase vs. Lovefield vs. Manticore Search vs. Yaacomo

System Properties Comparison Couchbase vs. Lovefield vs. Manticore Search vs. Yaacomo

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Yaacomo seems to be discontinued and is 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

Embeddable relational database for web apps written in pure JavaScript

Multi-storage database for search, including full-text search.

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

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

Time Series DBMS

using the Manticore Columnar Library

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

Score	16.59
Rank	#36	Overall
	#5	Document stores

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Website

www.couchbase.com

google.github.io/lovefield

manticoresearch.com

yaacomo.com

Technical documentation

docs.couchbase.com

github.com/google/lovefield/blob/master/docs/spec_index.md

manual.manticoresearch.com

Developer

Couchbase, Inc.

Google

Manticore Software

Q2WEB GmbH

Initial release

2011

2014

2017

2009

Current release

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

2.1.12, February 2017

6.0, February 2023

License

Commercial or Open Source

Open Source

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

Open Source

Apache 2.0

Open Source

GPL version 2

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

JavaScript

C++

Server operating systems

Linux
OS X
Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

FreeBSD
Linux
macOS
Windows

Android
Linux
Windows

Data scheme

schema-free

yes

Fixed schema

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

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

SQL-like query language

via JavaScript builder pattern

SQL-like query language

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

JDBC
ODBC

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

JavaScript

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

Server-side scripts

Stored procedures

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

user defined functions

Triggers

yes

via the TAP protocol

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

none

Sharding

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

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

none

Synchronous replication based on Galera library

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

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

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

yes

In-memory capabilities

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

yes

Ephemeral buckets

yes

using MemoryDB

yes

User concepts

Access control

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

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.