DBMS > Google BigQuery vs. Milvus vs. Oracle NoSQL vs. Tarantool vs. TimescaleDB

System Properties Comparison Google BigQuery vs. Milvus vs. Oracle NoSQL vs. Tarantool vs. TimescaleDB

Editorial information provided by DB-Engines

Name

Description

Large scale data warehouse service with append-only tables

A DBMS designed for efficient storage of vector data and vector similarity searches

A multi-model, scalable, distributed NoSQL database, designed to provide highly reliable, flexible, and available data management across a configurable set of storage nodes

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

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

Primary database model

Relational DBMS

Vector DBMS

Document store
Key-value store
Relational DBMS

Time Series DBMS

Secondary database models

Spatial DBMS

with Tarantool/GIS extension

Relational DBMS

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	2.31
Rank	#113	Overall
	#3	Vector DBMS

Score	2.95
Rank	#100	Overall
	#17	Document stores
	#17	Key-value stores
	#50	Relational DBMS

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

Score	4.64
Rank	#71	Overall
	#4	Time Series DBMS

Website

cloud.google.com/bigquery

milvus.io

www.oracle.com/database/nosql/technologies/nosql

www.tarantool.io

www.timescale.com

Technical documentation

cloud.google.com/bigquery/docs

milvus.io/docs/overview.md

docs.oracle.com/en/database/other-databases/nosql-database/index.html

www.tarantool.io/en/doc

docs.timescale.com

Developer

Google

Oracle

Timescale

Initial release

2010

2019

2011

2008

2017

Current release

2.3.4, January 2024

23.3, December 2023

2.10.0, May 2022

2.13.0, November 2023

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

Open Source

Proprietary for Enterprise Edition (Oracle Database EE license has Oracle NoSQL database EE covered: details)

Open Source

BSD-2, source-available extensions (modules), commercial licenses for Tarantool Enterprise

Open Source

Apache 2.0

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.

Zilliz Cloud – Cloud-native service for Milvus

Implementation language

C++, Go

Java

C and C++

Server operating systems

hosted

Linux
macOS

10.14 or later
Windows

with WSL 2 enabled

Linux
Solaris SPARC/x86

BSD
Linux
macOS

Linux
OS X
Windows

Data scheme

yes

Support Fixed schema and Schema-less deployment with the ability to interoperate between them.

Flexible data schema: relational definition for tables with ability to store json-like documents in columns

yes

Typing

predefined data types such as float or date

yes

Vector, Numeric and String

optional

string, double, decimal, uuid, integer, blob, boolean, datetime

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

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

Secondary indexes

yes

SQL

Support of SQL

yes

SQL-like DML and DDL statements

Full-featured ANSI SQL support

yes

full PostgreSQL SQL syntax

APIs and other access methods

RESTful HTTP/JSON API

RESTful HTTP API

Open binary protocol

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

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++
Go
Java
JavaScript (Node.js)
Python

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

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

.Net
C
C++
Delphi
Java

JDBC
JavaScript
Perl
PHP
Python
R
Ruby
Scheme
Tcl

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Lua, C and SQL stored procedures

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, before/after data modification events, on replication events, client session events

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Sharding, partitioned with virtual buckets by user defined affinity key. Live resharding for scale up and scale down without maintenance downtime.

yes, across time and space (hash partitioning) attributes

Replication methods

Methods for redundantly storing data on multiple nodes

Electable source-replica replication per shard. Support distributed global deployment with Multi-region table feature

Asynchronous replication with multi-master option
Configurable replication topology (full-mesh, chain, star)
Synchronous quorum replication (with Raft)

Source-replica replication with hot standby and reads on replicas

MapReduce

Offers an API for user-defined Map/Reduce methods

with Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Bounded Staleness
Eventual Consistency
Immediate Consistency
Session Consistency
Tunable Consistency

Eventual Consistency
Immediate Consistency

depending on configuration

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

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

configurable

ACID within a storage node (=shard)

ACID, with serializable isolation and linearizable read (within partition); Configurable MVCC (within partition); No cross-shard distributed transactions

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, cooperative multitasking

yes

Durability

Support for making data persistent

yes

yes, write ahead logging

yes

In-memory capabilities

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

yes

off heap cache

yes, full featured in-memory storage engine with persistence

User concepts

Access control

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

Google Cloud Identity & Access Management (IAM)

Role based access control and fine grained access rights

Access rights for users 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

fine grained access rights according to SQL-standard

More information provided by the system vendor

Specific characteristics

Milvus is an open-source and cloud-native vector database built for production-ready...
» more

Competitive advantages

Highly available, versatile, and robust with millisecond latency. Supports batch...
» more

Typical application scenarios

RAG: retrieval augmented generation Video media : video understanding, video deduplication....
» more

Key customers

Milvus is trusted by thousands of enterprises, including PayPal, eBay, IKEA, LINE,...
» more

Market metrics

As of January 2024, 25k+ GitHub stars 10M+ downloads and installations 3k+ enterprise...
» more

Licensing and pricing models

Milvus was released under the open-source Apache License 2.0 in October 2019. Fully-managed...
» 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.