DBMS > 4D vs. FatDB vs. IBM Db2 vs. VoltDB

System Properties Comparison 4D vs. FatDB vs. IBM Db2 vs. VoltDB

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

Application development environment with integrated database management system

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

Common in IBM host environments, 2 different versions for host and Windows/Linux

Distributed In-Memory NewSQL RDBMS

Used for OLTP applications with a high frequency of relatively simple transactions, that can hold all their data in memory

Primary database model

Relational DBMS

Document store
Key-value store

Relational DBMS

Since Version 10.5 support for JSON/BSON documents compatible with MongoDB

Relational DBMS

Secondary database models

Document store
RDF store

in Db2 LUW (Linux, Unix, Windows)
Spatial DBMS

with Db2 Spatial Extender

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

Score	2.47
Rank	#110	Overall
	#54	Relational DBMS

Score	125.90
Rank	#9	Overall
	#6	Relational DBMS

Score	1.47
Rank	#157	Overall
	#73	Relational DBMS

Website

www.4d.com

www.ibm.com/products/db2

www.voltdb.com

Technical documentation

developer.4d.com

www.ibm.com/docs/en/db2

docs.voltdb.com

Developer

4D, Inc

FatCloud

IBM

VoltDB Inc.

Initial release

1984

2012

1983

host version

2010

Current release

v20, April 2023

12.1, October 2016

11.3, April 2022

License

Commercial or Open Source

commercial

free version is available

Open Source

AGPL for Community Edition, commercial license for Enterprise, AWS, and Pro Editions

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

Java, C++

Server operating systems

OS X
Windows

Windows

AIX
HP-UX
Linux
Solaris
Windows
z/OS

Linux
OS X

for development

Data scheme

yes

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

Secondary indexes

yes

SQL

Support of SQL

yes

close to SQL 92

Via inetgration in SQL Server

yes

only a subset of SQL 99

APIs and other access methods

ODBC
RESTful HTTP API

by using 4D Mobile
SOAP webservices

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

ADO.NET
JDBC
JSON style queries

MongoDB compatible
ODBC
XQuery

Java API
JDBC
RESTful HTTP/JSON API

Supported programming languages

4D proprietary IDE
PHP

C
C#
C++
Cobol
Delphi
Fortran
Java
Perl
PHP
Python
Ruby
Visual Basic

C#
C++
Erlang

not officially supported
Go
Java
JavaScript

Node.js
PHP
Python

Server-side scripts

Stored procedures

yes

via applications

yes

Java

Triggers

yes

via applications

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

only with Windows/Unix/Linux Version

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

selectable replication factor

yes

with separate tools (MQ, InfoSphere)

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

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

FOREIGN KEY constraints are not supported

Transaction concepts

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

ACID

Transactions are executed single-threaded within stored procedures

Concurrency

Support for concurrent manipulation of data

yes

Data access is serialized by the server

Durability

Support for making data persistent

yes

Snapshots and command logging

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

User concepts

Access control

Users and groups

Can implement custom security layer via applications

fine grained access rights according to SQL-standard

Users and roles with access to stored procedures

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

MySQL, PostgreSQL and Redis are the winners of the March ranking
2 March 2016, Paul Andlinger

show all

Recent citations in the news

SAP and IBM Expand Partnership, Introduce Optimized DB2 Database
14 June 2024, br.ADVFN.com

Use AWS DMS to migrate data from IBM Db2 DPF to an AWS target | Amazon Web Services
28 May 2024, AWS Blog

Infotel Returns to IDUG North America 2024 in Charlotte to Showcase Latest Db2 Solutions and Feature Presentation ...
13 June 2024, PR Web

IBM Collaborates with AWS to Launch a New Cloud Database Offering, Enabling Customers to Optimize Data ...
27 November 2023, IBM Newsroom

IBM's vintage Db2 database jumps on AWS's cloud bandwagon
29 November 2023, The Register

provided by Google News

Unveiling Volt Active Data's game-changing approach to limitless app performance
16 October 2023, YourStory

VoltDB Launches Active(N) Lossless Cross Data Center Replication
31 August 2021, PR Newswire

VoltDB Turns to Real-Time Analytics with NewSQL Database
30 January 2014, Datanami

VoltDB Upgrades Power, Security of Its In-Memory Database
1 February 2017, eWeek

VoltDB Adds Geospatial Support, Cross-Site Replication
28 January 2016, The New Stack

provided by Google News

Share this page