DBMS > Badger vs. DataFS vs. FatDB

System Properties Comparison Badger vs. DataFS vs. FatDB

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

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

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

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

Primary database model

Key-value store

Object oriented DBMS

Document store
Key-value store

Secondary database models

Graph DBMS

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

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

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

Website

github.com/dgraph-io/badger

newdatabase.com

Technical documentation

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

dev.mobiland.com/Overview.xsp

Developer

DGraph Labs

Mobiland AG

FatCloud

Initial release

2017

2018

2012

Current release

1.1.263, October 2022

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

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

Server operating systems

BSD
Linux
OS X
Solaris
Windows

Windows

Data scheme

schema-free

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

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.

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

APIs and other access methods

.NET Client API
Proprietary client DLL
WinRT client

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

Supported programming languages

.Net
C
C#
C++
VB.Net

Server-side scripts

Stored procedures

yes

via applications

Triggers

no, except callback-events from server when changes happened

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

none

Proprietary Sharding system

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency

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

In-memory capabilities

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

User concepts

Access control

Windows-Profile

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