DBMS > Blueflood vs. Google Cloud Datastore vs. Lovefield vs. Microsoft Azure AI Search

System Properties Comparison Blueflood vs. Google Cloud Datastore vs. Lovefield vs. Microsoft Azure AI Search

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Scalable TimeSeries DBMS based on Cassandra

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

Embeddable relational database for web apps written in pure JavaScript

Search-as-a-service for web and mobile app development

Primary database model

Secondary database models

Vector DBMS

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

Score	0.09
Rank	#353	Overall
	#33	Time Series DBMS

Score	4.49
Rank	#79	Overall
	#12	Document stores

Score	0.32
Rank	#290	Overall
	#132	Relational DBMS

Score	5.71
Rank	#64	Overall
	#8	Search engines

Website

blueflood.io

cloud.google.com/datastore

google.github.io/lovefield

azure.microsoft.com/en-us/services/search

Technical documentation

github.com/rax-maas/blueflood/wiki

cloud.google.com/datastore/docs

github.com/google/lovefield/blob/master/docs/spec_index.md

learn.microsoft.com/en-us/azure/search

Developer

Rackspace

Google

Microsoft

Initial release

2013

2008

2014

2015

Current release

2.1.12, February 2017

License

Commercial or Open Source

Open Source

Apache 2.0

commercial

Open Source

Apache 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

Java

JavaScript

Server operating systems

Linux
OS X

hosted

server-less, requires a JavaScript environment (browser, Node.js)

tested with Chrome, Firefox, IE, Safari

hosted

Data scheme

predefined scheme

schema-free

yes

Typing

predefined data types such as float or date

yes

yes, details here

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

SQL

Support of SQL

SQL-like query language (GQL)

SQL-like query language

via JavaScript builder pattern

APIs and other access methods

HTTP REST

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

RESTful HTTP API

Supported programming languages

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

JavaScript

C#
Java
JavaScript
Python

Server-side scripts

Stored procedures

using Google App Engine

Triggers

Callbacks using the Google Apps Engine

Using read-only observers

Partitioning methods

Methods for storing different data on different nodes

Sharding

based on Cassandra

Sharding

none

Sharding

Implicit feature of the cloud service

Replication methods

Methods for redundantly storing data on multiple nodes

selectable replication factor

based on Cassandra

Multi-source replication using Paxos

none

yes

Implicit feature of the cloud service

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

based on Cassandra
Immediate Consistency

based on Cassandra

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.

Immediate 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

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

yes, by using IndexedDB or the cloud service Firebase Realtime Database

yes

In-memory capabilities

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

yes

using MemoryDB

User concepts

Access control

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

yes

using Azure authentication

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 is NOT magicking away data egress fees
12 January 2024, The Stack

SAP adds vector datastore to HANA Cloud database
2 November 2023, Techzine Europe

NetApp Cloud Volumes Service datastore support for Google Cloud VMware Engine
7 February 2023, NetApp

Your Memories. Their Cloud.
1 January 2023, The New York Times

All of Google’s cloud database services are now out of beta
16 August 2016, TechCrunch

provided by Google News

Announcing updates to Azure AI Search to help organizations build and scale generative AI applications
4 April 2024, Microsoft

Public Preview of Azure OpenAI and AI Search in-app connectors for Logic Apps (Standard) | Azure updates
2 April 2024, Microsoft

Microsoft’s Azure AI Search updated with increased storage, vector index size
5 April 2024, InfoWorld

Microsoft Azure AI adds storage power, large RAG app support
5 April 2024, VentureBeat

Microsoft Azure AI Search just got a massive storage increase - here's what you need to know
8 April 2024, ITPro

provided by Google News

Share this page