DBMS > Amazon Redshift vs. Datomic vs. Microsoft Azure Synapse Analytics vs. Sphinx vs. Sqrrl

System Properties Comparison Amazon Redshift vs. Datomic vs. Microsoft Azure Synapse Analytics vs. Sphinx vs. Sqrrl

Editorial information provided by DB-Engines

Name

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

Large scale data warehouse service for use with business intelligence tools

Datomic builds on immutable values, supports point-in-time queries and uses 3rd party systems for durability

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

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Relational DBMS

Search engine

Document store
Graph DBMS
Key-value store
Wide column store

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.59
Rank	#150	Overall
	#69	Relational DBMS

Score	20.56
Rank	#31	Overall
	#19	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

aws.amazon.com/redshift

www.datomic.com

azure.microsoft.com/services/synapse-analytics

sphinxsearch.com

sqrrl.com

Technical documentation

docs.aws.amazon.com/redshift

docs.datomic.com

docs.microsoft.com/azure/synapse-analytics

sphinxsearch.com/docs

Developer

Amazon (based on PostgreSQL)

Cognitect

Microsoft

Sphinx Technologies Inc.

Amazon

originally Sqrrl Data, Inc.

Initial release

2012

2016

2001

2012

Current release

1.0.6735, June 2023

3.5.1, February 2023

License

Commercial or Open Source

commercial

limited edition free

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, Clojure

C++

Java

Server operating systems

hosted

All OS with a Java VM

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux

Data scheme

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

yes

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

RESTful HTTP API

ADO.NET
JDBC
ODBC

Proprietary protocol

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

All languages supporting JDBC/ODBC

Clojure
Java

C#
Java
PHP

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

user defined functions

in Python

yes

Transaction Functions

Transact SQL

Triggers

By using transaction functions

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

But extensive use of caching in the application peers

Sharding, horizontal partitioning

Sharding

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

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

But extensive use of caching in the application peers

yes

none

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

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

Atomic updates per row, document, or graph entity

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using external storage systems (e.g. Cassandra, DynamoDB, PostgreSQL, Couchbase and others)

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

recommended only for testing and development

User concepts

Access control

fine grained access rights according to SQL-standard

yes

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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.