DBMS > FatDB vs. Google Cloud Datastore vs. Qdrant vs. Valentina Server

System Properties Comparison FatDB vs. Google Cloud Datastore vs. Qdrant vs. Valentina Server

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

FatDB/FatCloud has ceased operations as a company with February 2014. FatDB is discontinued and excluded from the ranking.

Description

A .NET NoSQL DBMS that can integrate with and extend SQL Server.

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

Object-relational database and reports server

Primary database model

Document store
Key-value store

Document store

Vector DBMS

Relational DBMS

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

Score	4.47
Rank	#76	Overall
	#12	Document stores

Score	1.16
Rank	#175	Overall
	#6	Vector DBMS

Score	0.17
Rank	#327	Overall
	#145	Relational DBMS

Website

cloud.google.com/datastore

github.com/qdrant/qdrant
qdrant.tech

www.valentina-db.net

Technical documentation

cloud.google.com/datastore/docs

qdrant.tech/documentation

valentina-db.com/docs/dokuwiki/v5/doku.php

Developer

FatCloud

Google

Qdrant

Paradigma Software

Initial release

2012

2008

2021

1999

Current release

5.7.5

License

Commercial or Open Source

commercial

Open Source

Apache Version 2.0

commercial

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

Server operating systems

Windows

hosted

Docker
Linux
macOS
Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

Numbers, Strings, Geo, Boolean

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.

Secondary indexes

yes

Keywords, numberic ranges, geo, full-text

yes

SQL

Support of SQL

Via inetgration in SQL Server

SQL-like query language (GQL)

yes

APIs and other access methods

.NET Client API
LINQ
RESTful HTTP API
RPC
Windows WCF Bindings

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

gRPC
OpenAPI 3.0
RESTful HTTP/JSON API

OpenAPI 3.0

ODBC

Supported programming languages

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

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

.Net
C
C#
C++
Objective-C
PHP
Ruby
Visual Basic
Visual Basic.NET

Server-side scripts

Stored procedures

yes

via applications

using Google App Engine

yes

Triggers

yes

via applications

Callbacks using the Google Apps Engine

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

Multi-source replication using Paxos

Collection-level 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

Eventual Consistency
Immediate Consistency

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

Foreign keys

Referential integrity

yes

via ReferenceProperties or Ancestor paths

yes

Transaction concepts

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

ACID

Serializable Isolation within Transactions, Read Committed outside of Transactions

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

Can implement custom security layer via applications

Access rights for users, groups and roles based on Google Cloud Identity and Access Management (IAM)

Key-based authentication

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.

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 Stops Exit Fees
12 January 2024, Spiceworks News and Insights

BigID Data Intelligence Platform Now Available on Google Cloud Marketplace
6 November 2023, PR Newswire

Inside Google’s strategic move to eliminate customer cloud data transfer fees
12 January 2024, Network World

Google says it'll stop charging fees to transfer data out of Google Cloud
11 January 2024, TechCrunch

What is Google App Engine? | Definition from TechTarget
26 April 2024, TechTarget

provided by Google News

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

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

Qdrant offers managed vector database for hybrid clouds
16 April 2024, InfoWorld

Qdrant launches first vector database as a managed hybrid cloud
16 April 2024, VentureBeat

Why Vector Data Services For AI Are A Moveable Feast
17 April 2024, Forbes

provided by Google News

A Look at Valentina — SitePoint
18 April 2014, SitePoint

MySQL GUI Tools for Windows and Ubuntu/Linux: Top 8 free or open source
7 December 2018, H2S Media

provided by Google News

Share this page