DBMS > EsgynDB vs. Lovefield vs. MySQL vs. PouchDB vs. VictoriaMetrics

System Properties Comparison EsgynDB vs. Lovefield vs. MySQL vs. PouchDB vs. VictoriaMetrics

Editorial information provided by DB-Engines

Name

Description

Enterprise-class SQL-on-Hadoop solution, powered by Apache Trafodion

Embeddable relational database for web apps written in pure JavaScript

Widely used open source RDBMS

JavaScript DBMS with an API inspired by CouchDB

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

Primary database model

Relational DBMS

Key/Value like access via memcached API

Document store

Time Series DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	0.15
Rank	#325	Overall
	#144	Relational DBMS

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Score	1029.49
Rank	#2	Overall
	#2	Relational DBMS

Score	2.18
Rank	#114	Overall
	#21	Document stores

Score	1.23
Rank	#165	Overall
	#15	Time Series DBMS

Website

www.esgyn.cn

google.github.io/lovefield

www.mysql.com

pouchdb.com

victoriametrics.com

Technical documentation

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

dev.mysql.com/doc

pouchdb.com/guides

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

Developer

Esgyn

Google

Oracle

since 2010, originally MySQL AB, then Sun

Apache Software Foundation

VictoriaMetrics

Initial release

2015

2014

1995

2012

2018

Current release

2.1.12, February 2017

9.0.0, July 2024

7.1.1, June 2019

v1.91, May 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are 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

C++, Java

JavaScript

C and C++

JavaScript

Server operating systems

Linux

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

tested with Chrome, Firefox, IE, Safari

FreeBSD
Linux
OS X
Solaris
Windows

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

FreeBSD
Linux
macOS
OpenBSD

Data scheme

yes

schema-free

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

via views

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

yes

with proprietary extensions

APIs and other access methods

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

HTTP REST

only for PouchDB Server
JavaScript API

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

Supported programming languages

All languages supporting JDBC/ODBC/ADO.Net

JavaScript

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

JavaScript

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

View functions in JavaScript

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication between multi datacenters

none

Multi-source replication
Source-replica replication

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

Synchronous replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

not for MyISAM storage engine

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

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

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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.