DBMS > Blueflood vs. EsgynDB vs. Lovefield vs. MySQL

System Properties Comparison Blueflood vs. EsgynDB vs. Lovefield vs. MySQL

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

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

Primary database model

Time Series DBMS

Relational DBMS

Key/Value like access via memcached API

Secondary database models

Document store
Spatial DBMS

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

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	0.16
Rank	#329	Overall
	#146	Relational DBMS

Score	0.29
Rank	#293	Overall
	#133	Relational DBMS

Score	1083.74
Rank	#2	Overall
	#2	Relational DBMS

Website

blueflood.io

www.esgyn.cn

google.github.io/lovefield

www.mysql.com

Technical documentation

github.com/rax-maas/blueflood/wiki

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

dev.mysql.com/doc

Developer

Rackspace

Esgyn

Google

Oracle

since 2010, originally MySQL AB, then Sun

Initial release

2013

2015

2014

1995

Current release

2.1.12, February 2017

8.4.0, April 2024

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

Open Source

GPL version 2. Commercial licenses with extended functionallity are available

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.

Aiven for MySQL: Fully managed MySQL, deployable in the cloud of your choice, with seamless integrations and lightning-fast setup.

Implementation language

Java

C++, Java

JavaScript

C and C++

Server operating systems

Linux
OS X

Linux

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

tested with Chrome, Firefox, IE, Safari

FreeBSD
Linux
OS X
Solaris
Windows

Data scheme

predefined scheme

yes

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

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

yes

with proprietary extensions

APIs and other access methods

HTTP REST

ADO.NET
JDBC
ODBC

ADO.NET
JDBC
ODBC
Proprietary native API

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

Server-side scripts

Stored procedures

Java Stored Procedures

yes

proprietary syntax

Triggers

Using read-only observers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

none

horizontal partitioning, sharding with MySQL Cluster or MySQL Fabric

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication between multi datacenters

none

Multi-source replication
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

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate 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

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

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.