DBMS > Badger vs. EJDB vs. FatDB vs. Manticore Search vs. Microsoft SQL Server

System Properties Comparison Badger vs. EJDB vs. FatDB vs. Manticore Search vs. Microsoft SQL Server

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.

Embeddable document-store database library with JSON representation of queries (in MongoDB style)

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

Multi-storage database for search, including full-text search.

Microsofts flagship relational DBMS

Primary database model

Key-value store

Document store

Document store
Key-value store

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store
Graph DBMS
Spatial 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.27
Rank	#297	Overall
	#44	Document stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Website

github.com/dgraph-io/badger

github.com/Softmotions/ejdb

manticoresearch.com

www.microsoft.com/en-us/sql-server

Technical documentation

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

github.com/Softmotions/ejdb/blob/master/README.md

manual.manticoresearch.com

learn.microsoft.com/en-US/sql/sql-server

Developer

DGraph Labs

Softmotions

FatCloud

Manticore Software

Microsoft

Initial release

2017

2012

2017

1989

Current release

6.0, February 2023

SQL Server 2022, November 2022

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPLv2

commercial

Open Source

GPL version 2

commercial

restricted free version is 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.

Implementation language

C++

Server operating systems

BSD
Linux
OS X
Solaris
Windows

server-less

Windows

FreeBSD
Linux
macOS
Windows

Linux
Windows

Data scheme

schema-free

Fixed schema

yes

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language

yes

APIs and other access methods

in-process shared library

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Supported programming languages

Actionscript
C
C#
C++
Go
Java
JavaScript (Node.js)
Lua
Objective-C
Pike
Python
Ruby

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

Server-side scripts

Stored procedures

yes

via applications

user defined functions

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

tables can be distributed across several files (horizontal partitioning); sharding through federation

Replication methods

Methods for redundantly storing data on multiple nodes

none

selectable replication factor

Synchronous replication based on Galera library

yes, but depending on the SQL-Server Edition

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

yes

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

yes

In-memory capabilities

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

yes

User concepts

Access control

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

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.