DBMS > AlaSQL vs. Couchbase vs. OrigoDB vs. VictoriaMetrics

System Properties Comparison AlaSQL vs. Couchbase vs. OrigoDB vs. VictoriaMetrics

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

JavaScript DBMS library

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

A fully ACID in-memory object graph database

A fast, cost-effective and scalable Time Series DBMS and monitoring solution

Primary database model

Document store
Relational DBMS

Document store

Document store
Object oriented DBMS

Time Series 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	0.46
Rank	#260	Overall
	#40	Document stores
	#121	Relational DBMS

Score	17.30
Rank	#36	Overall
	#5	Document stores

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

Score	1.32
Rank	#162	Overall
	#14	Time Series DBMS

Website

Technical documentation

github.com/AlaSQL/alasql

docs.couchbase.com

origodb.com/docs

docs.victoriametrics.com
github.com/VictoriaMetrics/VictoriaMetrics/wiki

Developer

Andrey Gershun & Mathias R. Wulff

Couchbase, Inc.

Robert Friberg et al

VictoriaMetrics

Initial release

2014

2011

2009

under the name LiveDB

2018

Current release

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

v1.91, May 2023

License

Commercial or Open Source

Open Source

MIT-License

Open Source

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

Open Source

Apache Version 2.0

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

JavaScript

C, C++, Go and Erlang

Server operating systems

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

Linux
OS X
Windows

Linux
Windows

FreeBSD
Linux
macOS
OpenBSD

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

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

Close to SQL99, but no user access control, stored procedures and host language bindings.

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

APIs and other access methods

JavaScript API

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

.NET Client API
HTTP API
LINQ

Graphite protocol
InfluxDB Line Protocol
OpenTSDB
Prometheus Query API
Prometheus Remote Read/Write

Supported programming languages

JavaScript

.Net
C
Go
Java
JavaScript

Node.js
Kotlin
PHP
Python
Ruby
Scala

.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

none

Automatic Sharding

horizontal partitioning

client side managed; servers are not synchronized

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

including cross data center replication
Source-replica replication

Source-replica replication

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

selectable on a per-operation basis

Eventual Consistency

Foreign keys

Referential integrity

yes

depending on model

Transaction concepts

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

yes

only for local storage and DOM-storage

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, SQL.JS or proprietary FileStorage

yes

Write ahead log

yes

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.

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.