DBMS > Google Cloud Datastore vs. Qdrant vs. searchxml vs. ToroDB

System Properties Comparison Google Cloud Datastore vs. Qdrant vs. searchxml vs. ToroDB

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

ToroDB seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

Automatically scaling NoSQL Database as a Service (DBaaS) on the Google Cloud Platform

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

DBMS for structured and unstructured content wrapped with an application server

A MongoDB-compatible JSON document store, built on top of PostgreSQL

Primary database model

Document store

Vector DBMS

Native XML DBMS
Search engine

Document store

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

Score	4.13
Rank	#71	Overall
	#12	Document stores

Score	1.53
Rank	#145	Overall
	#7	Vector DBMS

Score	0.00
Rank	#385	Overall
	#7	Native XML DBMS
	#24	Search engines

Website

cloud.google.com/datastore

github.com/qdrant/qdrant
qdrant.tech

www.searchxml.net/category/products

github.com/torodb/server

Technical documentation

cloud.google.com/datastore/docs

qdrant.tech/documentation

www.searchxml.net/support/handouts

Developer

Google

Qdrant

informationpartners gmbh

8Kdata

Initial release

2008

2021

2015

2016

Current release

1.0

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

Open Source

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

Rust

C++

Java

Server operating systems

hosted

Docker
Linux
macOS
Windows

Windows

All OS with a Java 7 VM

Data scheme

schema-free

Typing

predefined data types such as float or date

yes, details here

Numbers, Strings, Geo, Boolean

yes

string, integer, double, boolean, date, object_id

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

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

SQL-like query language (GQL)

APIs and other access methods

gRPC (using protocol buffers) API
RESTful HTTP/JSON API

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

RESTful HTTP API
WebDAV
XQuery
XSLT

Supported programming languages

.Net
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

using Google App Engine

yes

on the application server

Triggers

Callbacks using the Google Apps Engine

Partitioning methods

Methods for storing different data on different nodes

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication using Paxos

Collection-level replication

yes

sychronisation to multiple collections

Source-replica replication

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

using Google Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on type of query and configuration

Strong Consistency is default for entity lookups and queries within an Entity Group (but can instead be made eventually consistent). Other queries are always eventual consistent.

Eventual Consistency, tunable consistency

Immediate Consistency

Eventual Consistency
Immediate Consistency

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

multiple readers, single writer

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

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 rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Key-based authentication

Domain, group and role-based access control at the document level and for application services

Access rights for users and roles

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

Recent citations in the news

Google Cloud vs AWS: Which Cloud Computing Platform is Better?
11 September 2024, Cloudwards

Google Gets Rid of Fees To Transfer Data Out of Cloud Platform
12 January 2024, Spiceworks News and Insights

Google App Engine
26 April 2024, TechTarget

What Is Google Cloud? Platform, Benefits & More Explained
11 September 2024, Cloudwards

17 Top Cloud Storage Companies to Know
9 April 2024, Built In

provided by Google News

Qdrant review: A highly flexible option for vector search
29 July 2024, InfoWorld

Open source vector database startup Qdrant raises $28M
23 January 2024, TechCrunch

Vector database company Qdrant wants RAG to be more cost-effective
2 July 2024, VentureBeat

Qdrant Announces an Industry-First Hybrid Cloud Offering For Enterprise AI Applications
16 April 2024, Business Wire

Qdrant unveils hybrid vector algorithm for improved RAG
2 July 2024, Blocks & Files

provided by Google News

Share this page