DBMS > Brytlyt vs. InterSystems IRIS vs. Sphinx vs. TerminusDB

System Properties Comparison Brytlyt vs. InterSystems IRIS vs. Sphinx vs. TerminusDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable GPU-accelerated RDBMS for very fast analytic and streaming workloads, leveraging PostgreSQL

A containerised multi-model DBMS, interoperability and analytics data platform with wide capabilities for vertical and horizontal scalability

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

Scalable Graph Database platform making enterprise data available by exploiting inferred entities and relationships

Primary database model

Relational DBMS

Document store
Key-value store
Object oriented DBMS
Relational DBMS

Search engine

Graph DBMS

Secondary database models

Document store
RDF store

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

Score	0.28
Rank	#272	Overall
	#126	Relational DBMS

Score	2.25
Rank	#119	Overall
	#22	Document stores
	#23	Key-value stores
	#2	Object oriented DBMS
	#59	Relational DBMS

Score	7.29
Rank	#60	Overall
	#8	Search engines

Score	0.10
Rank	#314	Overall
	#29	Graph DBMS

Website

www.brytlyt.com

www.intersystems.com/products/intersystems-iris

sphinxsearch.com

terminusdb.com

Technical documentation

docs.intersystems.com/irislatest/csp/docbook/DocBook.UI.Page.cls

sphinxsearch.com/docs

terminusdb.github.io/terminusdb/#

Developer

Brytlyt

InterSystems

Sphinx Technologies Inc.

DataChemist Ltd.

Initial release

2016

2018

2001

2018

Current release

0.9, October 2016

2021.1, June 2021

3.4.1, July 2021

10.0.21, March 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2, commercial licence available

Open Source

GPL V3

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, C++ and CUDA

C++

Prolog, Rust

Server operating systems

Linux
OS X
Windows

AIX
Linux
macOS
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Linux

Data scheme

yes

depending on used data model

yes

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

specific XML-type available, but no XML query functionality.

yes

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

SQL-like query language (WOQL)

APIs and other access methods

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

JDBC
ODBC
RESTful HTTP API

Proprietary protocol

OWL
RESTful HTTP API
WOQL (Web Object Query Language)

Supported programming languages

.Net
C
C++
Delphi
Java
Perl
Python
Tcl

.Net
C++
Java
JavaScript (Node.js)
Python

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

JavaScript
Python

Server-side scripts

Stored procedures

user defined functions

in PL/pgSQL

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Graph Partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

Source-replica replication

none

Journaling Streams

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

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

yes

in-memory journaling

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

Role-based access control

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts