DBMS > Amazon Redshift vs. CouchDB vs. Interbase vs. NSDb vs. Sphinx

System Properties Comparison Amazon Redshift vs. CouchDB vs. Interbase vs. NSDb vs. Sphinx

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A native JSON - document store inspired by Lotus Notes, scalable from globally distributed server-clusters down to mobile phones.

Light-weight proven RDBMS

originally from Borland

Scalable, High-performance Time Series DBMS designed for Real-time Analytics on top of Kubernetes

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

Primary database model

Secondary database models

Spatial DBMS

using the Geocouch extension

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	8.30
Rank	#47	Overall
	#7	Document stores

Score	4.08
Rank	#75	Overall
	#41	Relational DBMS

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

aws.amazon.com/redshift

couchdb.apache.org

www.embarcadero.com/products/interbase

nsdb.io

sphinxsearch.com

Technical documentation

docs.aws.amazon.com/redshift

docs.couchdb.org/en/stable

docs.embarcadero.com/products/interbase

nsdb.io/Architecture

sphinxsearch.com/docs

Developer

Amazon (based on PostgreSQL)

Apache Software Foundation

Apache top-level project, originally developed by Damien Katz, a former Lotus Notes developer

Embarcadero

Sphinx Technologies Inc.

Initial release

2012

2005

1984

2017

2001

Current release

3.3.3, December 2023

InterBase 2020, December 2019

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2

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

Erlang

Java, Scala

C++

Server operating systems

hosted

Android
BSD
Linux
OS X
Solaris
Windows

Android
iOS
Linux
OS X
Windows

Linux
macOS

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

yes

schema-free

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

Secondary indexes

restricted

yes

via views

yes

all fields are automatically indexed

yes

full-text index on all search fields

SQL

Support of SQL

yes

does not fully support an SQL-standard

yes

SQL-like query language

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

RESTful HTTP/JSON API

ADO.NET
JDBC
ODBC

gRPC
HTTP REST
WebSocket

Proprietary protocol

Supported programming languages

All languages supporting JDBC/ODBC

C
C#
ColdFusion
Erlang
Haskell
Java
JavaScript
Lisp
Lua
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
Ruby
Smalltalk

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

Java
Scala

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

View functions in JavaScript

yes

Interbase procedure and trigger language

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

improved architecture with release 2.0

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Interbase Change Views

none

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

Eventual 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

atomic operations within a single document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

strategy: optimistic locking

yes

Multiversion concurreny control

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

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

Access rights for users can be defined per database

fine grained access rights according to SQL-standard

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.