DBMS > Google BigQuery vs. IBM Cloudant vs. NebulaGraph vs. Qdrant

System Properties Comparison Google BigQuery vs. IBM Cloudant vs. NebulaGraph vs. Qdrant

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

Database as a Service offering based on Apache CouchDB

A distributed, linear scalable, high perfomant Graph DBMS

A high-performance vector database with neural network or semantic-based matching

Primary database model

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

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	2.75
Rank	#104	Overall
	#19	Document stores

Score	2.23
Rank	#116	Overall
	#10	Graph DBMS

Score	1.28
Rank	#167	Overall
	#7	Vector DBMS

Website

cloud.google.com/bigquery

www.ibm.com/products/cloudant

github.com/vesoft-inc/nebula
www.nebula-graph.io

github.com/qdrant/qdrant
qdrant.tech

Technical documentation

cloud.google.com/bigquery/docs

cloud.ibm.com/docs/Cloudant

docs.nebula-graph.io

qdrant.tech/documentation

Developer

Google

IBM, Apache Software Foundation

IBM acquired Cloudant in February 2014

Vesoft Inc.

Qdrant

Initial release

2010

2019

2021

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0 + Common Clause 1.0

Open Source

Apache Version 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.

Implementation language

Erlang

C++

Rust

Server operating systems

hosted

Linux

Docker
Linux
macOS
Windows

Data scheme

yes

schema-free

Strong typed schema

schema-free

Typing

predefined data types such as float or date

yes

Numbers, Strings, Geo, Boolean

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.

Secondary indexes

yes

Nebula Graph internally uses the Key-Value store RocksDB for persistency. The vertices, edges, and their properties are stored as Key while their values are stored as Value. The primary indexes are per Key and secondary indexes are per Value.

yes

Keywords, numberic ranges, geo, full-text

SQL

Support of SQL

yes

SQL-like query language

APIs and other access methods

RESTful HTTP/JSON API

Browser interface
console (shell)
Cypher Query Language
GO Object Graph Mapper
Java Object Graph Mapper
NGBatis

ORM framework for NebulaGraph and Spring-Boot
Proprietary native API
Python Object Graph Mapper
Query language nGQL

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

Supported programming languages

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C#
Java
JavaScript
Objective-C
PHP
Ruby

.Net
C++
Go
Java
PHP
Python

.Net
Go
Java
JavaScript (Node.js)
Python
Rust

Server-side scripts

Stored procedures

user defined functions

in JavaScript

View functions (Map-Reduce) in JavaScript

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication
Source-replica replication

Causal Clustering using Raft protocol

Collection-level replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Immediate Consistency

Eventual Consistency, tunable consistency

Foreign keys

Referential integrity

yes

Relationships in graphs

Transaction concepts

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

Since BigQuery is designed for querying data

atomic operations within a document possible

ACID

Concurrency

Support for concurrent manipulation of data

yes

Optimistic locking

yes

Durability

Support for making data persistent

yes

using RocksDB

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)

Access rights for users can be defined per database

Role-based access control

Key-based authentication

More information provided by the system vendor

Specific characteristics

NebulaGraph is a truly distributed, linearly scalable, lightning-fast graph database,...
» more

Competitive advantages

NebulaGraph boasts the world's only graph database solution that is able to host...
» more

Typical application scenarios

Social networking Fraud detection Knowledge graph Data warehouse management Anti...
» more

Key customers

Companies from a variety of industries have implemented NebulaGraph Database in production,...
» more

Market metrics

At our very early stage, NebulaGraph has already received over 10,000 stars on GitHub...
» more

Licensing and pricing models

NebulaGraph is open source and free to use under Apache 2.0 license.
» 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.