DBMS > jBASE vs. Manticore Search vs. Redis vs. SingleStore vs. Tarantool

System Properties Comparison jBASE vs. Manticore Search vs. Redis vs. SingleStore vs. Tarantool

Editorial information provided by DB-Engines

Name

Description

A robust multi-value DBMS comprising development tools and middleware

Multi-storage database for search, including full-text search.

Popular in-memory data platform used as a cache, message broker, and database that can be deployed on-premises, across clouds, and hybrid environments

Redis focuses on performance so most of its design decisions prioritize high performance and very low latencies.

MySQL wire-compliant distributed RDBMS that combines an in-memory row-oriented and a disc-based column-oriented storage with patented universal storage to handle transactional and analytical workloads in one single table type

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

Primary database model

Multivalue DBMS

Search engine

Key-value store

Multiple data types and a rich set of operations, as well as configurable data expiration, eviction and persistence

Relational DBMS

Document store
Key-value store
Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Document store

with RedisJSON
Graph DBMS

with RedisGraph
Spatial DBMS
Search engine

with RediSearch
Time Series DBMS

with RedisTimeSeries
Vector DBMS

Document store
Spatial DBMS
Time Series DBMS
Vector DBMS

Spatial DBMS

with Tarantool/GIS extension

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

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	157.80
Rank	#6	Overall
	#1	Key-value stores

Score	5.60
Rank	#62	Overall
	#35	Relational DBMS

Score	1.72
Rank	#144	Overall
	#25	Document stores
	#25	Key-value stores
	#66	Relational DBMS

Website

www.rocketsoftware.com/products/rocket-multivalue-application-development-platform/rocket-jbase

Technical documentation

docs.rocketsoftware.com/bundle?labelkey=jbase_5.9

manual.manticoresearch.com

docs.redis.com/latest/index.html
redis.io/docs

docs.singlestore.com

www.tarantool.io/en/doc

Developer

Rocket Software (formerly Zumasys)

Manticore Software

Redis project core team, inspired by Salvatore Sanfilippo

Development sponsored by Redis Inc.

SingleStore Inc.

Initial release

1991

2017

2009

2013

2008

Current release

5.7

6.0, February 2023

7.2.4, January 2024

8.5, January 2024

2.10.0, May 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

source-available extensions (modules), commercial licenses for Redis Enterprise

commercial

free developer edition available

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 Redis: Fully managed in-memory key-value store for all your caching and speedy lookup needs.

SingleStoreDB Cloud: The world's fastest, modern cloud database for both operational (OLTP) and analytical (OLAP) workloads. Available instantly with multi-cloud and hybrid-cloud capabilities

Implementation language

C++

C++, Go

C and C++

Server operating systems

AIX
Linux
Windows

FreeBSD
Linux
macOS
Windows

BSD
Linux
OS X
Windows

ported and maintained by Microsoft Open Technologies, Inc.

Linux

64 bit version required

BSD
Linux
macOS

Data scheme

schema-free

Fixed schema

schema-free

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

optional

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

partial

Supported data types are strings, hashes, lists, sets and sorted sets, bit arrays, hyperloglogs and geospatial indexes

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.

yes

Can index from XML

Secondary indexes

yes

full-text index on all search fields

yes

with RediSearch module

yes

SQL

Support of SQL

Embedded SQL for jBASE in BASIC

SQL-like query language

with RediSQL module

yes

but no triggers and foreign keys

Full-featured ANSI SQL support

APIs and other access methods

JDBC
ODBC
Proprietary protocol
RESTful HTTP API
SOAP-based API

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

proprietary protocol

RESP - REdis Serialization Protocol

Cluster Management API

as HTTP Rest and CLI
HTTP API
JDBC
MongoDB API
ODBC

Open binary protocol

Supported programming languages

.Net
Basic
Jabbascript
Java

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

C
C#
C++
Clojure
Crystal
D
Dart
Elixir
Erlang
Fancy
Go
Haskell
Haxe
Java
JavaScript (Node.js)
Lisp
Lua
MatLab
Objective-C
OCaml
Pascal
Perl
PHP
Prolog
Pure Data
Python
R
Rebol
Ruby
Rust
Scala
Scheme
Smalltalk
Swift
Tcl
Visual Basic

Bash
C
C#
Java
JavaScript (Node.js)
Python

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

Server-side scripts

Stored procedures

yes

user defined functions

Lua; Redis Functions coming in Redis 7 (slides and Github)

yes

Lua, C and SQL stored procedures

Triggers

yes

publish/subscribe channels provide some trigger functionality; RedisGears

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

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Automatic hash-based sharding with support for hash-tags for manual sharding

Sharding

hash partitioning

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

Synchronous replication based on Galera library

Multi-source replication

with Redis Enterprise Pack
Source-replica replication

Chained replication is supported

Source-replica replication

stores two copies of each physical data partition on two separate nodes

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

through RedisGears

can define user-defined aggregate functions for map-reduce-style calculations

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency
Causal consistency can be enabled in Active-Active databases
Strong consistency with Redis Raft
Strong eventual consistency with Active-Active

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

yes

isolated transactions for atomic changes and binary logging for safe writes

Atomic execution of command blocks and scripts and optimistic locking

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

Data access is serialized by the server

yes, multi-version concurrency control (MVCC)

yes, cooperative multitasking

Durability

Support for making data persistent

yes

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

yes

Configurable mechanisms for persistency via snapshots and/or operations logs

yes

All updates are persistent, including those to disk-based columnstores and memory-based row stores. Transaction commits are supported via write-ahead log.

yes, write ahead logging

In-memory capabilities

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

yes

yes, full featured in-memory storage engine with persistence

User concepts

Access control

Access rights can be defined down to the item level

Access Control Lists (ACLs): redis.io/docs/management/security/acl
LDAP and Role-Based Access Control (RBAC) for Redis Enterprise
Mutual TLS authentication: redis.io/docs/management/security/encryption
Password-based authentication

Fine grained access control via users, groups and roles

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

SingleStore offers a fully-managed , distributed, highly-scalable SQL database designed...
» more

Competitive advantages

SingleStore’s competitive advantages include: Easy and Simplified Architecture with...
» more

Typical application scenarios

Driving Fast Analytics: SingleStore delivers the fastest and most scalable reporting...
» more

Key customers

IEX Cloud : Improves Financial Data Distribution Speed 15x with Singlestore DB Comcast,...
» more

Market metrics

Customers in various industries worldwide including US and International Industry...
» more

Licensing and pricing models

F ree Tier and Enterprise Edition
» 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.