DBMS > EJDB vs. FatDB

System Properties Comparison EJDB vs. FatDB

Please select another system to include it in the comparison.

Our visitors often compare EJDB and FatDB with SQLite, InfluxDB and Databricks.

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

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.

Primary database model

Document store

Document store
Key-value store

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

Score	0.27
Rank	#297	Overall
	#44	Document stores

Website

github.com/Softmotions/ejdb

Technical documentation

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

Developer

Softmotions

FatCloud

Initial release

2012

License

Commercial or Open Source

Open Source

GPLv2

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

server-less

Windows

Data scheme

schema-free

Typing

predefined data types such as float or date

yes

string, integer, double, bool, date, object_id

yes

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

APIs and other access methods

in-process shared library

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

Supported programming languages

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

Server-side scripts

Stored procedures

yes

via applications

Triggers

yes

via applications

Partitioning methods

Methods for storing different data on different nodes

none

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

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

typically not needed, however similar functionality with collection joins possible

Transaction concepts

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

Concurrency

Support for concurrent manipulation of data

yes

Read/Write Locking

yes

Durability

Support for making data persistent

yes

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