DBMS > Google BigQuery vs. Manticore Search vs. Memcached vs. OpenTSDB

System Properties Comparison Google BigQuery vs. Manticore Search vs. Memcached vs. OpenTSDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

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

In-memory key-value store, originally intended for caching

Scalable Time Series DBMS based on HBase

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	0.29
Rank	#302	Overall
	#21	Search engines

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	1.68
Rank	#142	Overall
	#12	Time Series DBMS

Website

cloud.google.com/bigquery

manticoresearch.com

www.memcached.org

opentsdb.net

Technical documentation

cloud.google.com/bigquery/docs

manual.manticoresearch.com

github.com/memcached/memcached/wiki

opentsdb.net/docs/build/html/index.html

Developer

Google

Manticore Software

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

currently maintained by Yahoo and other contributors

Initial release

2010

2017

2003

2011

Current release

6.0, February 2023

1.6.27, May 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

BSD license

Open Source

LGPL

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++

Java

Server operating systems

hosted

FreeBSD
Linux
macOS
Windows

FreeBSD
Linux
OS X
Unix
Windows

Linux
Windows

Data scheme

yes

Fixed schema

schema-free

Typing

predefined data types such as float or date

yes

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

numeric data for metrics, strings for tags

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

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

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

Proprietary protocol

HTTP API
Telnet API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

Erlang
Go
Java
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

Triggers

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

none

Repcached, a Memcached patch, provides this functionallity

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

based on HBase

Foreign keys

Referential integrity

Transaction concepts

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

Since BigQuery is designed for querying data

yes

isolated transactions for atomic changes and binary logging for safe writes

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.

User concepts

Access control

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

yes

using SASL (Simple Authentication and Security Layer) protocol

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.