DBMS > KeyDB vs. Machbase Neo vs. Microsoft SQL Server vs. Sphinx

System Properties Comparison KeyDB vs. Machbase Neo vs. Microsoft SQL Server vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

An ultra-fast, open source Key-value store fully compatible with Redis API, modules, and protocols

TimeSeries DBMS for AIoT and BigData

Microsofts flagship relational DBMS

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

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	0.80
Rank	#219	Overall
	#31	Key-value stores

Score	0.22
Rank	#324	Overall
	#29	Time Series DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

github.com/Snapchat/KeyDB
keydb.dev

machbase.com

www.microsoft.com/en-us/sql-server

sphinxsearch.com

Technical documentation

docs.keydb.dev

machbase.com/dbms

learn.microsoft.com/en-US/sql/sql-server

sphinxsearch.com/docs

Developer

EQ Alpha Technology Ltd.

Machbase

Microsoft

Sphinx Technologies Inc.

Initial release

2019

2013

1989

2001

Current release

V8.0, August 2023

SQL Server 2022, November 2022

3.5.1, February 2023

License

Commercial or Open Source

Open Source

BSD-3

commercial

free test version available

commercial

restricted free version is available

Open Source

GPL version 2, commercial licence available

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

Linux

Linux
macOS
Windows

Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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.

yes

Secondary indexes

yes

by using the Redis Search module

yes

full-text index on all search fields

SQL

Support of SQL

SQL-like query language

yes

SQL-like query language (SphinxQL)

APIs and other access methods

Proprietary protocol

RESP - REdis Serialization Protoco

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Proprietary protocol

Supported programming languages

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

Lua

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

selectable replication factor

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Strong eventual consistency with CRDTs

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Optimistic locking, atomic execution of commands blocks and scripts

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

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

volatile and lookup table

yes

User concepts

Access control

simple password-based access control and ACL

simple password-based access control

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.