DBMS > FatDB vs. Interbase vs. Postgres-XL vs. Vitess

System Properties Comparison FatDB vs. Interbase vs. Postgres-XL vs. Vitess

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.

Light-weight proven RDBMS

originally from Borland

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

Scalable, distributed, cloud-native DBMS, extending MySQL

Primary database model

Document store
Key-value store

Relational DBMS

Secondary database models

Document store
Spatial DBMS

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

Score	3.78
Rank	#77	Overall
	#41	Relational DBMS

Score	0.43
Rank	#260	Overall
	#119	Relational DBMS

Score	0.86
Rank	#202	Overall
	#95	Relational DBMS

Website

www.embarcadero.com/products/interbase

www.postgres-xl.org

vitess.io

Technical documentation

docs.embarcadero.com/products/interbase

www.postgres-xl.org/documentation

vitess.io/docs

Developer

FatCloud

Embarcadero

The Linux Foundation, PlanetScale

Initial release

2012

1984

2014

since 2012, originally named StormDB

2013

Current release

InterBase 2020, December 2019

10 R1, October 2018

15.0.2, December 2022

License

Commercial or Open Source

commercial

Open Source

Mozilla public license

Open Source

Apache Version 2.0, commercial licenses 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

Server operating systems

Windows

Android
iOS
Linux
OS X
Windows

Linux
macOS

Docker
Linux
macOS

Data scheme

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.

export as XML data possible

yes

XML type, but no XML query functionality

Secondary indexes

yes

SQL

Support of SQL

Via inetgration in SQL Server

yes

distributed, parallel query execution

yes

with proprietary extensions

APIs and other access methods

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

ADO.NET
JDBC
ODBC

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

ADO.NET
JDBC
MySQL protocol
ODBC

Supported programming languages

.Net
C
C++
Delphi
Java
Object Pascal
PHP
Ruby

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

Ada
C
C#
C++
D
Delphi
Eiffel
Erlang
Haskell
Java
JavaScript (Node.js)
Objective-C
OCaml
Perl
PHP
Python
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

yes

via applications

yes

Interbase procedure and trigger language

user defined functions

yes

proprietary syntax

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

horizontal partitioning

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Interbase Change Views

Multi-source replication
Source-replica replication

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 across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

not for MyISAM storage engine

Transaction concepts

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

ACID

MVCC

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

Multiversion concurreny control

yes

table locks or row locks depending on storage engine

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.

yes

User concepts

Access control

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

Users with fine-grained authorization concept

no user groups or roles

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

Recent citations in the news

An independent soccer league transforming lives in a slum in Kenya
15 November 2022, FanSided

7 Visual Studio Tools to Improve Your Software Development in 2021
30 September 2021, hackernoon.com

The advance of Air Force Esports
25 June 2023, New Zealand Defence Force

Malaysian e-commerce firm Lelong.my acquires local digital marketing agency Mataris Agency
29 January 2018, Yahoo Singapore News

iResidenz cracks an elusive market
6 September 2017, Digital News Asia

provided by Google News

Deepthi Sigireddi on Distributed Database Architecture in the Cloud Native Era
20 May 2024, InfoQ.com

They scaled YouTube — now they’ll shard everyone with PlanetScale
13 December 2018, TechCrunch

PlanetScale Unveils Distributed MySQL Database Service Based on Vitess
18 May 2021, Datanami

PlanetScale offers undo button to reverse schema migration without losing data
24 March 2022, The Register

CNCF’s Vitess Scales MySQL with the Help of Kubernetes
9 February 2018, The New Stack

provided by Google News

Share this page