DBMS > IBM Cloudant vs. Lovefield vs. SQLite vs. YDB

System Properties Comparison IBM Cloudant vs. Lovefield vs. SQLite vs. YDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Database as a Service offering based on Apache CouchDB

Embeddable relational database for web apps written in pure JavaScript

Widely used embeddable, in-process RDBMS

A distributed fault-tolerant database service, with high availability, scalability, immediate consistency and ACID transactions and providing an Amazon DynamoDB compatible API

Primary database model

Document store

Relational DBMS

Document store
Relational DBMS

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

Score	2.85
Rank	#95	Overall
	#18	Document stores

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Score	0.39
Rank	#269	Overall
	#43	Document stores
	#126	Relational DBMS

Website

www.ibm.com/products/cloudant

google.github.io/lovefield

www.sqlite.org

github.com/ydb-platform/ydb
ydb.tech

Technical documentation

cloud.ibm.com/docs/Cloudant

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

www.sqlite.org/docs.html

ydb.tech/en/docs

Developer

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Google

Dwayne Richard Hipp

Yandex

Initial release

2010

2014

2000

2019

Current release

2.1.12, February 2017

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

Public Domain

Open Source

Apache 2.0; commercial license available

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

JavaScript

Server operating systems

hosted

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

tested with Chrome, Firefox, IE, Safari

server-less

Linux

Data scheme

schema-free

yes

dynamic column types

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

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like query language

via JavaScript builder pattern

yes

SQL-92 is not fully supported

SQL-like query language (YQL)

APIs and other access methods

RESTful HTTP/JSON API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

RESTful HTTP API (DynamoDB compatible)

Supported programming languages

C#
Java
JavaScript
Objective-C
PHP
Ruby

JavaScript

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

Go
Java
JavaScript (Node.js)
PHP
Python

Server-side scripts

Stored procedures

View functions (Map-Reduce) in JavaScript

Triggers

yes

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

Active-passive shard 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

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

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

yes

In-memory capabilities

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

yes

using MemoryDB

yes

User concepts

Access control

Access rights for users can be defined per database

Access rights defined for Yandex Cloud users

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.