DBMS > Apache Phoenix vs. Lovefield vs. Microsoft SQL Server vs. Sphinx vs. Yanza

System Properties Comparison Apache Phoenix vs. Lovefield vs. Microsoft SQL Server vs. Sphinx vs. Yanza

Editorial information provided by DB-Engines

Name

Yanza seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A scale-out RDBMS with evolutionary schema built on Apache HBase

Embeddable relational database for web apps written in pure JavaScript

Microsofts flagship relational DBMS

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

Time Series DBMS for IoT Applications

Primary database model

Relational DBMS

Search engine

Time Series DBMS

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	2.02
Rank	#130	Overall
	#63	Relational DBMS

Score	0.32
Rank	#290	Overall
	#132	Relational DBMS

Score	829.80
Rank	#3	Overall
	#3	Relational DBMS

Score	6.03
Rank	#60	Overall
	#6	Search engines

Website

phoenix.apache.org

google.github.io/lovefield

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

sphinxsearch.com

yanza.com

Technical documentation

phoenix.apache.org

github.com/google/lovefield/blob/master/docs/spec_index.md

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

sphinxsearch.com/docs

Developer

Apache Software Foundation

Google

Microsoft

Sphinx Technologies Inc.

Yanza

Initial release

2014

1989

2001

2015

Current release

5.0-HBase2, July 2018 and 4.15-HBase1, December 2019

2.1.12, February 2017

SQL Server 2022, November 2022

3.5.1, February 2023

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

Apache 2.0

commercial

restricted free version is available

Open Source

GPL version 2, commercial licence available

commercial

free version available

Cloud-based only

Only available as a cloud service

but mainly used as a service provided by Yanza

DBaaS offerings (sponsored links)

Database as a Service

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

Implementation language

Java

JavaScript

C++

Server operating systems

Linux
Unix
Windows

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Windows

Data scheme

yes

late-bound, schema-on-read capabilities

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.

yes

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language

via JavaScript builder pattern

yes

SQL-like query language (SphinxQL)

APIs and other access methods

JDBC

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

Proprietary protocol

HTTP API

Supported programming languages

C
C#
C++
Go
Groovy
Java
PHP
Python
Scala

JavaScript

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

any language that supports HTTP calls

Server-side scripts

Stored procedures

user defined functions

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

Triggers

Using read-only observers

yes

Timer and event based

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

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

Sharding

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

none

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

none

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

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

yes, by using IndexedDB or the cloud service Firebase Realtime Database

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

using MemoryDB

yes

User concepts

Access control

Access Control Lists (using HBase ACL) for RBAC, integration with Apache Ranger for RBAC & ABAC, multi-tenancy

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.