DBMS > Google BigQuery vs. Manticore Search vs. TimescaleDB vs. Typesense

System Properties Comparison Google BigQuery vs. Manticore Search vs. TimescaleDB vs. Typesense

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.

A time series DBMS optimized for fast ingest and complex queries, based on PostgreSQL

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Relational DBMS

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	4.46
Rank	#71	Overall
	#5	Time Series DBMS

Score	0.76
Rank	#219	Overall
	#14	Search engines

Website

cloud.google.com/bigquery

manticoresearch.com

www.timescale.com

typesense.org

Technical documentation

cloud.google.com/bigquery/docs

manual.manticoresearch.com

docs.timescale.com

typesense.org/docs

Developer

Google

Manticore Software

Timescale

Initial release

2010

2017

2015

Current release

6.0, February 2023

2.15.0, May 2024

License

Commercial or Open Source

commercial

Open Source

GPL version 2

Open Source

Apache 2.0

Open Source

GPL V3

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

FreeBSD
Linux
macOS
Windows

Linux
OS X
Windows

Linux

Data scheme

yes

Fixed schema

yes

schema-free

pre-defined schema optional

Typing

predefined data types such as float or date

yes

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

numerics, strings, booleans, arrays, JSON blobs, geospatial dimensions, currencies, binary data, other complex data types

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

SQL

Support of SQL

yes

SQL-like query language

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP/JSON API

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

ADO.NET
JDBC
native C library
ODBC
streaming API for large objects

RESTful HTTP API

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

user defined functions, PL/pgSQL, PL/Tcl, PL/Perl, PL/Python, PL/Java, PL/PHP, PL/R, PL/Ruby, PL/Scheme, PL/Unix shell

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

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

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

Source-replica replication with hot standby and reads on replicas

Multi-source replication using RAFT

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

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

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

In-memory capabilities

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

yes

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

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.