DBMS > Amazon Redshift vs. NSDb vs. PlanetScale vs. Sphinx vs. Valentina Server

System Properties Comparison Amazon Redshift vs. NSDb vs. PlanetScale vs. Sphinx vs. Valentina Server

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

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

Scalable, distributed, serverless MySQL database platform built on top of Vitess

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

Object-relational database and reports server

Primary database model

Secondary database models

Document store
Spatial DBMS

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	0.08
Rank	#369	Overall
	#40	Time Series DBMS

Score	1.49
Rank	#155	Overall
	#72	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.21
Rank	#325	Overall
	#144	Relational DBMS

Website

aws.amazon.com/redshift

Technical documentation

docs.aws.amazon.com/redshift

nsdb.io/Architecture

planetscale.com/docs

sphinxsearch.com/docs

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

Amazon (based on PostgreSQL)

PlanetScale

Sphinx Technologies Inc.

Paradigma Software

Initial release

2012

2017

2020

2001

1999

Current release

3.5.1, February 2023

5.7.5

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

GPL version 2, commercial licence available

commercial

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

Java, Scala

C++

Server operating systems

hosted

Linux
macOS

Docker
Linux
macOS

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

Typing

predefined data types such as float or date

yes

yes: int, bigint, decimal, string

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

all fields are automatically indexed

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

SQL-like query language

yes

with proprietary extensions

SQL-like query language (SphinxQL)

yes

APIs and other access methods

JDBC
ODBC

gRPC
HTTP REST
WebSocket

ADO.NET
JDBC
MySQL protocol
ODBC

Proprietary protocol

ODBC

Supported programming languages

All languages supporting JDBC/ODBC

Java
Scala

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

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

user defined functions

in Python

yes

proprietary syntax

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

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

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Eventual Consistency across shards
Immediate Consistency within a shard

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

yes

not for MyISAM storage engine

yes

Transaction concepts

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

ACID

ACID at shard level

Concurrency

Support for concurrent manipulation of data

yes

table locks or row locks depending on storage engine

yes

Durability

Support for making data persistent

yes

Using Apache Lucene

yes

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

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

Users with fine-grained authorization concept

no user groups or roles

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.