DBMS > IBM Cloudant vs. SQLite vs. ToroDB vs. VictoriaMetrics vs. Warp 10

System Properties Comparison IBM Cloudant vs. SQLite vs. ToroDB vs. VictoriaMetrics vs. Warp 10

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Database as a Service offering based on Apache CouchDB

Widely used embeddable, in-process RDBMS

A MongoDB-compatible JSON document store, built on top of PostgreSQL

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.23
Rank	#172	Overall
	#15	Time Series DBMS

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

www.ibm.com/products/cloudant

www.sqlite.org

github.com/torodb/server

victoriametrics.com

www.warp10.io

Technical documentation

cloud.ibm.com/docs/Cloudant

www.sqlite.org/docs.html

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

www.warp10.io/content/02_Getting_started

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Dwayne Richard Hipp

8Kdata

VictoriaMetrics

SenX

Initial release

2010

2000

2016

2018

2015

Current release

3.46.0 (23 May 2024), May 2024

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

Public Domain

Open Source

AGPL-V3

Open Source

Apache Version 2.0

Open Source

Apache License 2.0

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

Erlang

Java

Server operating systems

hosted

server-less

All OS with a Java 7 VM

FreeBSD
Linux
macOS
OpenBSD

Linux
OS X
Windows

Data scheme

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes

string, integer, double, boolean, date, object_id

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

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

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

HTTP API
Jupyter
WebSocket

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

yes

WarpScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Source-replica replication

Synchronous replication

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

Transaction concepts

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

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

via file-system locks

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

User concepts

Access control

Access rights for users can be defined per database

Access rights for users and roles

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.