DBMS > EventStoreDB vs. FatDB vs. Heroic vs. Lovefield

System Properties Comparison EventStoreDB vs. FatDB vs. Heroic vs. Lovefield

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

Industrial-strength, open-source database solution built from the ground up for event sourcing.

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Embeddable relational database for web apps written in pure JavaScript

Primary database model

Event Store

Document store
Key-value store

Time Series DBMS

Relational DBMS

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

Score	1.07
Rank	#181	Overall
	#1	Event Stores

Score	0.13
Rank	#335	Overall
	#29	Time Series DBMS

Score	0.22
Rank	#306	Overall
	#138	Relational DBMS

Website

www.eventstore.com

github.com/spotify/heroic

google.github.io/lovefield

Technical documentation

developers.eventstore.com

spotify.github.io/heroic

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

Developer

Event Store Limited

FatCloud

Spotify

Google

Initial release

2012

2014

Current release

21.2, February 2021

2.1.12, February 2017

License

Commercial or Open Source

Open Source

commercial

Open Source

Apache 2.0

Open Source

Apache 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

Java

JavaScript

Server operating systems

Linux
Windows

Windows

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

tested with Chrome, Firefox, IE, Safari

Data scheme

schema-free

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

HQL (Heroic Query Language, a JSON-based language)
HTTP API

Supported programming languages

JavaScript

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

via applications

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes

none

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

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

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

Can implement custom security layer via applications

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

Share this page