DBMS > Blueflood vs. JaguarDB vs. Manticore Search vs. PouchDB vs. Snowflake

System Properties Comparison Blueflood vs. JaguarDB vs. Manticore Search vs. PouchDB vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

Performant, highly scalable DBMS for AI and IoT applications

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

JavaScript DBMS with an API inspired by CouchDB

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

Time Series DBMS

Key-value store
Vector 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	0.13
Rank	#346	Overall
	#33	Time Series DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	2.34
Rank	#112	Overall
	#21	Document stores

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

Technical documentation

github.com/rax-maas/blueflood/wiki

www.jaguardb.com/support.html

manual.manticoresearch.com

pouchdb.com/guides

docs.snowflake.net/manuals/index.html

Developer

Rackspace

DataJaguar, Inc.

Manticore Software

Apache Software Foundation

Snowflake Computing Inc.

Initial release

2013

2015

2017

2012

2014

Current release

3.3 July 2023

6.0, February 2023

7.1.1, June 2019

License

Commercial or Open Source

Open Source

Apache 2.0

Open Source

GPL V3.0

Open Source

GPL version 2

Open Source

commercial

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

Java

C++

the server part. Clients available in other languages

C++

JavaScript

Server operating systems

Linux
OS X

Linux

FreeBSD
Linux
macOS
Windows

server-less, requires a JavaScript environment (browser, Node.js)

hosted

Data scheme

predefined scheme

yes

Fixed schema

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

yes

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

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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

via views

SQL

Support of SQL

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

SQL-like query language

yes

APIs and other access methods

HTTP REST

JDBC
ODBC

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

HTTP REST

only for PouchDB Server
JavaScript API

CLI Client
JDBC
ODBC

Supported programming languages

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

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

JavaScript

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

View functions in JavaScript

user defined functions

Triggers

yes

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

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

Sharding

with a proxy-based framework, named couchdb-lounge

yes

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication

Synchronous replication based on Galera library

Multi-source replication

also with CouchDB databases
Source-replica replication

also with CouchDB databases

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Eventual Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

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

yes

by using IndexedDB, WebSQL or LevelDB as backend

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

rights management via user accounts

Users with fine-grained authorization concept, user roles and pluggable authentication

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.