DBMS > Amazon Redshift vs. LevelDB vs. Microsoft Azure Synapse Analytics vs. Sphinx vs. Warp 10

System Properties Comparison Amazon Redshift vs. LevelDB vs. Microsoft Azure Synapse Analytics vs. Sphinx vs. Warp 10

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

Embeddable fast key-value storage library that provides an ordered mapping from string keys to string values

Elastic, large scale data warehouse service leveraging the broad eco-system of SQL Server

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

TimeSeries DBMS specialized on timestamped geo data based on LevelDB or HBase

Primary database model

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

Score	16.88
Rank	#35	Overall
	#22	Relational DBMS

Score	2.25
Rank	#115	Overall
	#19	Key-value stores

Score	19.93
Rank	#31	Overall
	#19	Relational DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Score	0.14
Rank	#344	Overall
	#32	Time Series DBMS

Website

aws.amazon.com/redshift

github.com/google/leveldb

azure.microsoft.com/services/synapse-analytics

sphinxsearch.com

www.warp10.io

Technical documentation

docs.aws.amazon.com/redshift

github.com/google/leveldb/blob/main/doc/index.md

docs.microsoft.com/azure/synapse-analytics

sphinxsearch.com/docs

www.warp10.io/content/02_Getting_started

Developer

Amazon (based on PostgreSQL)

Google

Microsoft

Sphinx Technologies Inc.

SenX

Initial release

2012

2011

2016

2001

2015

Current release

1.23, February 2021

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

BSD

commercial

Open Source

GPL version 2, commercial licence available

Open Source

Apache License 2.0

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

Java

Server operating systems

hosted

Illumos
Linux
OS X
Windows

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux
OS X
Windows

Data scheme

yes

schema-free

yes

schema-free

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 query language (SphinxQL)

APIs and other access methods

JDBC
ODBC

ADO.NET
JDBC
ODBC

Proprietary protocol

HTTP API
Jupyter
WebSocket

Supported programming languages

All languages supporting JDBC/ODBC

C++
Go
Java

3rd party binding
JavaScript (Node.js)

3rd party binding
Python

3rd party binding

C#
Java
PHP

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

Transact SQL

yes

WarpScript

Triggers

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, horizontal partitioning

Sharding

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

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

yes

none

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-table-constraints

Transaction concepts

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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

with automatic compression on writes

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

yes

Mandatory use of cryptographic tokens, containing fine-grained authorizations

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.