DBMS > FatDB vs. Microsoft SQL Server vs. Postgres-XL vs. PouchDB

System Properties Comparison FatDB vs. Microsoft SQL Server vs. Postgres-XL vs. PouchDB

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

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

Microsofts flagship relational DBMS

Based on PostgreSQL enhanced with MPP and write-scale-out cluster features

JavaScript DBMS with an API inspired by CouchDB

Primary database model

Document store
Key-value store

Relational DBMS

Document store

Secondary database models

Document store
Graph DBMS
Spatial DBMS

Document store
Spatial DBMS

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

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	0.49
Rank	#256	Overall
	#117	Relational DBMS

Score	2.28
Rank	#115	Overall
	#21	Document stores

Website

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

www.postgres-xl.org

pouchdb.com

Technical documentation

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

www.postgres-xl.org/documentation

pouchdb.com/guides

Developer

FatCloud

Microsoft

Apache Software Foundation

Initial release

2012

1989

2014

since 2012, originally named StormDB

2012

Current release

SQL Server 2022, November 2022

10 R1, October 2018

7.1.1, June 2019

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Mozilla public license

Open Source

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++

JavaScript

Server operating systems

Windows

Linux
Windows

Linux
macOS

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

Data scheme

schema-free

yes

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.

yes

XML type, but no XML query functionality

Secondary indexes

yes

via views

SQL

Support of SQL

Via inetgration in SQL Server

yes

distributed, parallel query execution

APIs and other access methods

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

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

HTTP REST

only for PouchDB Server
JavaScript API

Supported programming languages

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

.Net
C
C++
Delphi
Erlang
Java
JavaScript (Node.js)
Perl
PHP
Python
Tcl

JavaScript

Server-side scripts

Stored procedures

yes

via applications

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

user defined functions

View functions in JavaScript

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

horizontal partitioning

Sharding

with a proxy-based framework, named couchdb-lounge

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

yes, but depending on the SQL-Server Edition

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

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

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

MVCC

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

by using IndexedDB, WebSQL or LevelDB as backend

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.