DBMS > Amazon Redshift vs. BigObject vs. FatDB vs. Vertica

System Properties Comparison Amazon Redshift vs. BigObject vs. FatDB vs. Vertica

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

Large scale data warehouse service for use with business intelligence tools

Analytic DBMS for real-time computations and queries

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

Cloud or off-cloud analytical database and query engine for structured and semi-structured streaming and batch data. Machine learning platform with built-in algorithms, data preparation capabilities, and model evaluation and management via SQL or Python.

Primary database model

Relational DBMS

a hierachical model (tree) can be imposed

Document store
Key-value store

Relational DBMS

Column oriented

Secondary database models

Spatial DBMS
Time Series DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.19
Rank	#329	Overall
	#146	Relational DBMS

Score	10.06
Rank	#42	Overall
	#26	Relational DBMS

Website

aws.amazon.com/redshift

bigobject.io

www.vertica.com

Technical documentation

docs.aws.amazon.com/redshift

docs.bigobject.io

vertica.com/documentation

Developer

Amazon (based on PostgreSQL)

BigObject, Inc.

FatCloud

OpenText

previously Micro Focus and Hewlett Packard

Initial release

2012

2015

2012

2005

Current release

12.0.3, January 2023

License

Commercial or Open Source

commercial

free community edition available

commercial

Limited community edition free

Cloud-based only

Only available as a cloud service

yes

on-premises, all major clouds - Amazon AWS, Microsoft Azure, Google Cloud Platform and containers

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

hosted

Linux

distributed as a docker-image
OS X

distributed as a docker-image (boot2docker)
Windows

distributed as a docker-image (boot2docker)

Windows

Linux

Data scheme

yes

schema-free

Yes, but also semi-structure/unstructured data storage, and complex hierarchical data (like Parquet) stored and/or queried.

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.

Secondary indexes

restricted

yes

No Indexes Required. Different internal optimization strategy, but same functionality included.

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like DML and DDL statements

Via inetgration in SQL Server

Full 1999 standard plus machine learning, time series and geospatial. Over 650 functions.

APIs and other access methods

JDBC
ODBC

fluentd
ODBC
RESTful HTTP API

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

ADO.NET
JDBC
Kafka Connector
ODBC
RESTful HTTP API
Spark Connector
vSQL

character-based, interactive, front-end utility

Supported programming languages

All languages supporting JDBC/ODBC

C#
C++
Go
Java
JavaScript (Node.js)
Perl
PHP
Python
R

Server-side scripts

Stored procedures

user defined functions

in Python

Lua

yes

via applications

yes, PostgreSQL PL/pgSQL, with minor differences

Triggers

yes

via applications

yes, called Custom Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

horizontal partitioning, hierarchical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

selectable replication factor

Multi-source replication

One, or more copies of data replicated across nodes, or object-store used for repository.

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Bi-directional Spark integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

none

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

automatically between fact table and dimension tables

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Read/write lock on objects (tables, trees)

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.

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Can implement custom security layer via applications

fine grained access rights according to SQL-standard; supports Kerberos, LDAP, Ident and hash

More information provided by the system vendor

Specific characteristics

Deploy-anywhere database for large-scale analytical deployments. Deploy off-cloud,...
» more

Competitive advantages

Fast, scalable, and capable of high concurrency. Separation of compute/storage leverages...
» more

Typical application scenarios

Communication and network analytics, Embedded analytics, Fraud monitoring and Risk...
» more

Key customers

Abiba Systems, Adform, adMarketplace, AmeriPride, Anritsu, AOL, Avito, Auckland Transport,...
» more

Licensing and pricing models

Cost-based models and subscription-based models are both available. One license is...
» more

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.