DBMS > Amazon Redshift vs. jBASE vs. Manticore Search vs. Sequoiadb

System Properties Comparison Amazon Redshift vs. jBASE vs. Manticore Search vs. Sequoiadb

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service for use with business intelligence tools

A robust multi-value DBMS comprising development tools and middleware

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

NewSQL database with distributed OLTP and SQL

Primary database model

Relational DBMS

Multivalue DBMS

Search engine

Document store
Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	17.94
Rank	#34	Overall
	#21	Relational DBMS

Score	1.41
Rank	#159	Overall
	#3	Multivalue DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	0.45
Rank	#261	Overall
	#41	Document stores
	#122	Relational DBMS

Website

aws.amazon.com/redshift

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

manticoresearch.com

www.sequoiadb.com

Technical documentation

docs.aws.amazon.com/redshift

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

manual.manticoresearch.com

www.sequoiadb.com/en/index.php?m=Files&a=index

Developer

Amazon (based on PostgreSQL)

Rocket Software (formerly Zumasys)

Manticore Software

Sequoiadb Ltd.

Initial release

2012

1991

2017

2013

Current release

5.7

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

Server: AGPL; Client: Apache V2

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

C++

Server operating systems

hosted

AIX
Linux
Windows

FreeBSD
Linux
macOS
Windows

Linux

Data scheme

yes

schema-free

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

optional

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

yes

oid, date, timestamp, binary, regex

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

restricted

yes

full-text index on all search fields

yes

SQL

Support of SQL

yes

does not fully support an SQL-standard

Embedded SQL for jBASE in BASIC

SQL-like query language

APIs and other access methods

JDBC
ODBC

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 using JSON

Supported programming languages

All languages supporting JDBC/ODBC

.Net
Basic
Jabbascript
Java

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

.Net
C++
Java
PHP
Python

Server-side scripts

Stored procedures

user defined functions

in Python

yes

user defined functions

JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

yes

informational only, not enforced by the system

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

Document is locked during a transaction

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 Manticore index.

yes

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

Access rights can be defined down to the item level

simple password-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.