DBMS > OpenSearch vs. Realm vs. Tarantool

System Properties Comparison OpenSearch vs. Realm vs. Tarantool

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

In-memory computing platform with a flexible data schema for efficiently building high-performance applications

Primary database model

Search engine

Document store

Document store
Key-value store
Relational DBMS

Secondary database models

Vector DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	12.61
Rank	#46	Overall
	#4	Search engines

Score	8.10
Rank	#55	Overall
	#10	Document stores

Score	1.86
Rank	#162	Overall
	#26	Document stores
	#28	Key-value stores
	#76	Relational DBMS

Website

github.com/opensearch-project
opensearch.org

realm.io

www.tarantool.io

Technical documentation

opensearch.org/docs/latest

realm.io/docs

www.tarantool.io/en/doc

Developer

Amazon Web Services

Realm, acquired by MongoDB in May 2019

Initial release

2021

2014

2008

Current release

2.5.0, January 2023

2.10.0, May 2022

License

Commercial or Open Source

Open Source

Apache Version 2.0

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

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 including search engine, NoSQL document database, and visualization interface.

Implementation language

Java

C and C++

Server operating systems

All OS with a Java VM

Android
Backend: server-less
iOS
Windows

BSD
Linux
macOS

Data scheme

schema-free

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

yes

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

Typing

predefined data types such as float or date

yes

string, double, decimal, uuid, integer, blob, boolean, datetime

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

SQL-like query language

Full-featured ANSI SQL support

APIs and other access methods

Java API
RESTful HTTP/JSON API

Open binary protocol

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

Elasticsearch client

.Net
Java

with Android only
Objective-C
React Native
Swift

C
C#
C++
Erlang
Go
Java
JavaScript
Lua
Perl
PHP
Python
Rust

Server-side scripts

Stored procedures

yes

runs within the applications so server-side scripts are unnecessary

Lua, C and SQL stored procedures

Triggers

yes

by using the 'percolation' feature

yes

Change Listeners

yes, before/after data modification events, on replication events, client session events

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

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

Immediate Consistency

Casual consistency across sharding partitions
Eventual consistency within replicaset partition

when using asyncronous replication
Immediate Consistency within single instance
Sequential consistency including linearizable read within replicaset partition

when using Raft

Foreign keys

Referential integrity

yes

Transaction concepts

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

ACID

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

Durability

Support for making data persistent

yes

yes, write ahead logging

In-memory capabilities

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

yes

In-Memory realm

yes, full featured in-memory storage engine with persistence

User concepts

Access control

yes

Access Control Lists
Mutual TLS authentication for Tarantol Enterprise
Password based authentication
Role-based access control (RBAC) and LDAP for Tarantol Enterprise
Users and Roles

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

OpenSearch is used across a broad range of search, analytics, and observability applications....
» 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.