DBMS > Couchbase vs. Coveo vs. Hyprcubd vs. mSQL vs. OrigoDB

System Properties Comparison Couchbase vs. Coveo vs. Hyprcubd vs. mSQL vs. OrigoDB

Editorial information provided by DB-Engines

Name

Hyprcubd seems to be discontinued. Therefore it is excluded 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

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Serverless Time Series DBMS

mSQL (Mini SQL) is a simple and lightweight RDBMS

A fully ACID in-memory object graph database

Primary database model

Document store
Object oriented 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	17.30
Rank	#36	Overall
	#5	Document stores

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	1.27
Rank	#167	Overall
	#77	Relational DBMS

Score	0.00
Rank	#383	Overall
	#53	Document stores
	#20	Object oriented DBMS

Website

www.couchbase.com

www.coveo.com

hyprcubd.com (offline)

hughestech.com.au/products/msql

origodb.com

Technical documentation

docs.couchbase.com

docs.coveo.com

origodb.com/docs

Developer

Couchbase, Inc.

Coveo

Hyprcubd, Inc.

Hughes Technologies

Robert Friberg et al

Initial release

2011

2012

1994

2009

under the name LiveDB

Current release

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

4.4, October 2021

License

Commercial or Open Source

Open Source

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

commercial

free licenses can be provided

Open Source

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

C, C++, Go and Erlang

Server operating systems

Linux
OS X
Windows

hosted

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

Linux
Windows

Data scheme

schema-free

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

yes

Typing

predefined data types such as float or date

yes

time, int, uint, float, string

yes

User defined using .NET types and collections

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 be achieved using .NET

Secondary indexes

yes

SQL

Support of SQL

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

SQL-like query language

A subset of ANSI SQL is implemented

no subqueries, aggregate functions, views, foreign keys, triggers

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

RESTful HTTP API

gRPC (https)

JDBC
ODBC

.NET Client API
HTTP API
LINQ

Supported programming languages

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

C#
Java
JavaScript
Python

C
C++
Delphi
Java
Perl
PHP
Tcl

.Net

Server-side scripts

Stored procedures

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

yes

Triggers

yes

via the TAP protocol

yes

Domain Events

Partitioning methods

Methods for storing different data on different nodes

Automatic Sharding

yes

none

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

including cross data center replication
Source-replica replication

yes

none

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

Eventual Consistency

none

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

ACID

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Write ahead log

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.

granular access controls, API key management, content filters

token access

Role based authorization

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.