DBMS > Badger vs. Google Cloud Firestore vs. Heroic vs. KeyDB

System Properties Comparison Badger vs. Google Cloud Firestore vs. Heroic vs. KeyDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An embeddable, persistent, simple and fast Key-Value Store, written purely in Go.

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

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

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

Primary database model

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

Score	0.14
Rank	#331	Overall
	#49	Key-value stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	0.71
Rank	#226	Overall
	#33	Key-value stores

Website

github.com/dgraph-io/badger

firebase.google.com/products/firestore

github.com/spotify/heroic

github.com/Snapchat/KeyDB
keydb.dev

Technical documentation

godoc.org/github.com/dgraph-io/badger

firebase.google.com/docs/firestore

spotify.github.io/heroic

docs.keydb.dev

Developer

DGraph Labs

Google

Spotify

EQ Alpha Technology Ltd.

Initial release

2017

2014

2019

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

Open Source

BSD-3

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

Java

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

hosted

Linux

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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

by using the Redis Search module

SQL

Support of SQL

APIs and other access methods

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

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

Proprietary protocol

RESP - REdis Serialization Protoco

Supported programming languages

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

Lua

Triggers

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

Multi-source replication

yes

Multi-source replication
Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

Eventual Consistency
Immediate Consistency

Eventual Consistency
Strong eventual consistency with CRDTs

Foreign keys

Referential integrity

Transaction concepts

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

yes

Optimistic locking, atomic execution of commands blocks and scripts

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

simple password-based access control and ACL

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.

More resources

DB-Engines blog posts

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Recent citations in the news

Realtime vs Cloud Firestore: Which Firebase Database to go?
8 March 2024, Appinventiv

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

Google's Cloud Firestore is now generally available
31 January 2019, ZDNet

Google launches Cloud Firestore, a new document database for app developers
3 October 2017, TechCrunch

Google's Cloud-Native NoSQL Database Cloud Firestore Is Now Generally Available
8 February 2019, InfoQ.com

provided by Google News

Oh, snap! Snap snaps up database developer KeyDB
12 May 2022, TechCrunch

Snap Acquires KeyDB for Open-Source Services
17 May 2022, XR Today

Garnet–open-source faster cache-store speeds up applications, services
18 March 2024, Microsoft

Microsoft open-sources Garnet cache-store -- a Redis rival?
19 March 2024, The Stack

Redis 6 arrives with multithreading for faster I/O
30 April 2020, InfoWorld

provided by Google News

Share this page