DBMS > Faircom DB vs. OpenSearch vs. Realm vs. STSdb

System Properties Comparison Faircom DB vs. OpenSearch vs. Realm vs. STSdb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Native high-speed multi-model DBMS for relational and key-value store data simultaneously accessible through SQL and NoSQL APIs.

A distributed, RESTful search and analytics engine forked from Elasticsearch and based on Apache Lucene

A DBMS built for use on mobile devices that’s a fast, easy to use alternative to SQLite and Core Data

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Key-value store
Relational DBMS

Search engine

Document store

Key-value store

Secondary database models

Vector DBMS

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

Score	0.24
Rank	#311	Overall
	#44	Key-value stores
	#140	Relational DBMS

Score	15.65
Rank	#38	Overall
	#4	Search engines

Score	7.71
Rank	#52	Overall
	#9	Document stores

Score	0.06
Rank	#365	Overall
	#55	Key-value stores

Website

www.faircom.com/products/faircom-db

github.com/opensearch-project
opensearch.org

realm.io

github.com/STSSoft/STSdb4

Technical documentation

docs.faircom.com/docs/en/UUID-7446ae34-a1a7-c843-c894-d5322e395184.html

opensearch.org/docs/latest

realm.io/docs

Developer

FairCom Corporation

Amazon Web Services

Realm, acquired by MongoDB in May 2019

STS Soft SC

Initial release

1979

2021

2014

2011

Current release

V12, November 2020

2.5.0, January 2023

4.0.8, September 2015

License

Commercial or Open Source

commercial

Restricted, free version available

Open Source

Apache Version 2.0

Open Source

GPLv2, commercial license 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.

Aiven for OpenSearch: Fully managed open source search and analytics suite. Out-of-the-box integrations get you up and running in a couple of clicks.

Implementation language

ANSI C, C++

Java

Server operating systems

AIX
FreeBSD
HP-UX
Linux
NetBSD
OS X
QNX
SCO
Solaris
VxWorks
Windows

easily portable to other OSs

All OS with a Java VM

Android
Backend: server-less
iOS
Windows

Windows

Data scheme

schema free, schema optional, schema required, partial schema,

schema-free

Flexible type definitions. Once a type is defined, it is persistent

yes

Typing

predefined data types such as float or date

yes, ANSI SQL Types, JSON, typed binary structures

yes

primitive types and user defined types (classes)

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

All search fields are automatically indexed

yes

SQL

Support of SQL

yes, ANSI SQL with proprietary extensions

SQL-like query language

APIs and other access methods

ADO.NET
Direct SQL
JDBC
JPA
ODBC
RESTful HTTP/JSON API
RESTful MQTT/JSON API
RPC

Java API
RESTful HTTP/JSON API

.NET Client API

Supported programming languages

.Net
C
C#
C++
Java
JavaScript (Node.js and browser)
PHP
Python
Visual Basic

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

.Net
Java

with Android only
Objective-C
React Native
Swift

C#
Java

Server-side scripts

Stored procedures

yes

.Net, JavaScript, C/C++

yes

runs within the applications so server-side scripts are unnecessary

Triggers

yes

by using the 'percolation' feature

yes

Change Listeners

Partitioning methods

Methods for storing different data on different nodes

File partitioning, horizontal partitioning, sharding

Customizable business rules for table partitioning

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes, configurable to be parallel or serial, synchronous or asynchronous, uni-directional or bi-directional, ACID-consistent or eventually consistent (with custom conflict resolution).

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Immediate Consistency
Tunable consistency per server, database, table, and transaction

Eventual Consistency

Synchronous doc based replication. Get by ID may show delays up to 1 sec. Configurable write consistency: one, quorum, all

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

tunable from ACID to Eventually Consistent

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Yes, tunable from durable to delayed durability to in-memory

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

yes

In-Memory realm

User concepts

Access control

Fine grained access rights according to SQL-standard with additional protections for files

yes

More information provided by the system vendor

Specific characteristics

OpenSearch is a highly scalable and extensible open-source software suite for search,...
» more

Competitive advantages

Distributed as fully open source under Apache License, Version 2.0 (ALv2), OpenSearch...
» more

Typical application scenarios

The OpenSearch platform is used across a broad range of search , analytics, and observability...
» more

Licensing and pricing models

The OpenSearch Project offers open source software licensed under Apache License...
» 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.