DBMS > Brytlyt vs. CrateDB vs. FatDB vs. PostGIS

System Properties Comparison Brytlyt vs. CrateDB vs. FatDB vs. PostGIS

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

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

Distributed Database based on Lucene

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

Spatial extension of PostgreSQL

Primary database model

Relational DBMS

Document store
Spatial DBMS
Search engine
Time Series DBMS
Vector DBMS

Document store
Key-value store

Spatial DBMS

Secondary database models

Relational DBMS

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

Score	0.27
Rank	#292	Overall
	#132	Relational DBMS

Score	0.69
Rank	#226	Overall
	#37	Document stores
	#5	Spatial DBMS
	#16	Search engines
	#19	Time Series DBMS
	#11	Vector DBMS

Score	20.16
Rank	#29	Overall
	#1	Spatial DBMS

Website

brytlyt.io

cratedb.com

postgis.net

Technical documentation

docs.brytlyt.io

cratedb.com/docs

postgis.net/documentation

Developer

Brytlyt

Crate

FatCloud

Initial release

2016

2013

2012

2005

Current release

5.0, August 2023

5.8.1, August 2024

3.4.2, February 2024

License

Commercial or Open Source

commercial

Open Source

commercial

Open Source

GPL v2.0

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, C++ and CUDA

Java

Server operating systems

Linux
OS X
Windows

All Operating Systems, including Kubernetes with CrateDB Kubernetes Operator support

Windows

Data scheme

yes

Flexible Schema (defined schema, partial schema, schema free)

schema-free

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.

yes

Secondary indexes

yes

SQL

Support of SQL

yes

yes, but no triggers and constraints, and PostgreSQL compatibility

Via inetgration in SQL Server

yes

APIs and other access methods

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

ADO.NET
JDBC
ODBC
PostgreSQL wire protocol
Prometheus Remote Read/Write
RESTful HTTP API

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

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.NET
Erlang
Go

community maintained client
Java
JavaScript (Node.js)

community maintained client
Perl

community maintained client
PHP
Python
R
Ruby

community maintained client
Scala

community maintained client

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

user defined functions (Javascript)

yes

via applications

user defined functions

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

yes

based on PostgreSQL

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

Configurable replication on table/partition-level

selectable replication factor

yes

based on PostgreSQL

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency
Read-after-write consistency on record level

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

unique row identifiers can be used for implementing an optimistic concurrency control strategy

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

fine grained access rights according to SQL-standard

rights management via user accounts

Can implement custom security layer via applications

yes

based on PostgreSQL

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.

More resources

DB-Engines blog posts

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Opensignal Announces Acquisition of Brytlyt GPU-based Data Analytics & Visualization Technology
5 June 2024, PR Web

Brytlyt releases version 5.0, introducing a more intuitive, intelligent and flexible analytics platform
1 August 2023, PR Newswire

Bringing GPUs To Bear On Bog Standard Relational Databases
26 February 2018, The Next Platform

London’s Brytlyt raises €4.4 million for its data analytics and visualisation technology
22 December 2021, EU-Startups

Brytlyt Unleashes Serverless GPU-Acceleration for Analytics
15 September 2021, PR Newswire

provided by Google News

CrateDB Appoints Jeff Olson as New CRO
9 July 2024, PR Newswire

CrateDB Announces Availability of CrateDB on Google Cloud Marketplace
8 April 2024, Datanami

Taleo Consulting and CrateDB Announce Strategic Partnership to Transform Data Management and Analytics in Financial Services markets
29 July 2024, PR Newswire

How We Designed CrateDB as a Realtime SQL DBMS for the Internet of Things
29 August 2017, The New Stack

CrateDB Appoints Sergey Gerasimenko as New CTO
19 February 2024, PR Newswire

provided by Google News

Share this page