DBMS > HEAVY.AI vs. Sphinx vs. SQLite vs. YugabyteDB

System Properties Comparison HEAVY.AI vs. Sphinx vs. SQLite vs. YugabyteDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A high performance, column-oriented RDBMS, specifically developed to harness the massive parallelism of modern CPU and GPU hardware

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

Widely used embeddable, in-process RDBMS

High-performance distributed SQL database for global, internet-scale applications. Wire and feature compatible with PostgreSQL.

Primary database model

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Spatial DBMS

Document store
Wide column store

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

Score	1.77
Rank	#141	Overall
	#65	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	2.91
Rank	#102	Overall
	#51	Relational DBMS

Website

github.com/heavyai/heavydb
www.heavy.ai

sphinxsearch.com

www.sqlite.org

www.yugabyte.com

Technical documentation

docs.heavy.ai

sphinxsearch.com/docs

www.sqlite.org/docs.html

docs.yugabyte.com
github.com/yugabyte/yugabyte-db

Developer

HEAVY.AI, Inc.

Sphinx Technologies Inc.

Dwayne Richard Hipp

Yugabyte Inc.

Initial release

2016

2001

2000

2017

Current release

5.10, January 2022

3.5.1, February 2023

3.45.3 (15 April 2024), April 2024

2.19, September 2023

License

Commercial or Open Source

Open Source

Apache Version 2; enterprise edition available

Open Source

GPL version 2, commercial licence available

Open Source

Public Domain

Open Source

Apache 2.0

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.

YugabyteDB Managed is the fully managed database-as-a-service offering of YugabyteDB. Get started quickly, and effortlessly ensure continuous availability and limitless scale of your cloud native applications.

Implementation language

C++ and CUDA

C++

C and C++

Server operating systems

Linux

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

server-less

Linux
OS X

Data scheme

yes

dynamic column types

depending on used data model

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

yes

SQL-92 is not fully supported

yes, PostgreSQL compatible

APIs and other access methods

JDBC
ODBC
Thrift
Vega

Proprietary protocol

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

JDBC
YCQL, an SQL-based flexible-schema API with its roots in Cassandra Query Language
YSQL - a fully relational SQL API that is wire compatible with the SQL language in PostgreSQL

Supported programming languages

All languages supporting JDBC/ODBC/Thrift
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

C
C#
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Rust
Scala

Server-side scripts

Stored procedures

yes

sql, plpgsql, C

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Round robin

Sharding

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

none

Hash and Range Sharding, row-level geo-partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

none

Based on Raft distributed consensus protocol, minimum 3 replicas for continuous availability

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Strong consistency on writes and tunable consistency on reads

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

Distributed ACID with Serializable & Snapshot Isolation. Inspired by Google Spanner architecture.

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

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

yes

based on RocksDB

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

More information provided by the system vendor

Specific characteristics

YugabyteDB is an open source distributed SQL database for cloud native transactional...
» more

Competitive advantages

PostgreSQL compatible: Get instantly productive with a PostgreSQL compatible RDBMS....
» more

Typical application scenarios

Systems of record and engagement for cloud native applications that require resilience,...
» more

Market metrics

2 Million+ lifetime clusters deployed, 6.5K+ GitHub stars, 7K YugabyteDB Community...
» more

Licensing and pricing models

Apache 2.0 license for the database
» more

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.