DBMS > FatDB vs. GreptimeDB vs. PostgreSQL

System Properties Comparison FatDB vs. GreptimeDB vs. PostgreSQL

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.

An open source Time Series DBMS built for increased scalability, high performance and efficiency

Widely used open source RDBMS

Developed as objectoriented DBMS (Postgres), gradually enhanced with 'standards' like SQL

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

with object oriented extensions, e.g.: user defined types/functions and inheritance. Handling of key/value pairs with hstore module.

Secondary database models

Document store
Graph DBMS

with Apache Age
Spatial DBMS
Vector DBMS

with pgvector extension

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

Score	0.15
Rank	#325	Overall
	#29	Time Series DBMS

Score	674.32
Rank	#4	Overall
	#4	Relational DBMS

Website

greptime.com

www.postgresql.org

Technical documentation

docs.greptime.com

www.postgresql.org/docs

Developer

FatCloud

Greptime Inc.

PostgreSQL Global Development Group

www.postgresql.org/developer

Initial release

2012

2022

1989

1989: Postgres, 1996: PostgreSQL

Current release

16.4, August 2024

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

BSD

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.

PostgreSQL Flex @ STACKIT offers managed PostgreSQL Instances with adjustable CPU, RAM, storage amount and speed and several extensions available, in enterprise grade to perfectly match all application requirements. All 100% GDPR-compliant.

Implementation language

Rust

Server operating systems

Windows

Android
Docker
FreeBSD
Linux
macOS
Windows

FreeBSD
HP-UX
Linux
NetBSD
OpenBSD
OS X
Solaris
Unix
Windows

Data scheme

schema-free

schema-free, schema definition possible

yes

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

specific XML-type available, but no XML query functionality.

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

standard with numerous extensions

APIs and other access methods

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

gRPC
HTTP API
JDBC

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

Supported programming languages

C++
Erlang
Go
Java
JavaScript

.Net
C
C++
Delphi
Java

JDBC
JavaScript (Node.js)
Perl
PHP
Python
Tcl

Server-side scripts

Stored procedures

yes

via applications

Python

user defined functions

realized in proprietary language PL/pgSQL or with common languages like Perl, Python, Tcl etc.

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

partitioning by range, list and (since PostgreSQL 11) by hash

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Source-replica replication

other methods possible by using 3rd party extensions

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

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

Can implement custom security layer via applications

Simple rights management via user accounts

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.