DBMS > Amazon Redshift vs. Fujitsu Enterprise Postgres vs. Immudb vs. Sphinx

System Properties Comparison Amazon Redshift vs. Fujitsu Enterprise Postgres vs. Immudb vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Enterprise-grade PostgreSQL-based DBMS with security enhancements such as Transparent Data Encryption and Data Masking, plus high-availability and performance improvement features.

An open source immutable (append-only) database with cryptographic verification which makes it tamper-resistant and fully auditable.

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Relational DBMS

Key-value store

Search engine

Secondary database models

Document store
Spatial DBMS

Relational DBMS

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	0.31
Rank	#285	Overall
	#129	Relational DBMS

Score	0.24
Rank	#305	Overall
	#43	Key-value stores

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

aws.amazon.com/redshift

www.postgresql.fastware.com

github.com/codenotary/immudb
immudb.io

sphinxsearch.com

Technical documentation

docs.aws.amazon.com/redshift

www.postgresql.fastware.com/product-manuals

docs.immudb.io

sphinxsearch.com/docs

Developer

Amazon (based on PostgreSQL)

PostgreSQL Global Development Group, Fujitsu Australia Software Technology

Codenotary

Sphinx Technologies Inc.

Initial release

2012

2020

2001

Current release

Fujitsu Enterprise Postgres 14, January 2022

1.2.3, April 2022

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

GPL version 2, commercial licence available

Cloud-based only

Only available as a cloud service

yes

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
Windows

BSD
Linux
macOS
Solaris
Windows
z/OS

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

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.

Secondary indexes

restricted

yes

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like syntax

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

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

gRPC protocol
PostgreSQL wire protocol

Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

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

.Net
Go
Java
JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in Python

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

partitioning by range, list and by hash

Sharding

Partitioning is done manually, search queries against distributed index is supported

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Sphinx index.

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

More information provided by the system vendor

Specific characteristics

100% compatible with community PostgreSQL
» more

Competitive advantages

Built-in TDE and Data Masking security. In-Memory Columnar Index, and a high speed...
» more

Typical application scenarios

Transactional payments applications, reporting and mixed workloads.
» more

Market metrics

Over 30 years experience in database technology. Over 20 years in Postgres development...
» more

Licensing and pricing models

Core based licensing
» 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.