DBMS > Coveo vs. Firebase Realtime Database vs. Lovefield vs. Machbase Neo vs. Snowflake

System Properties Comparison Coveo vs. Firebase Realtime Database vs. Lovefield vs. Machbase Neo vs. Snowflake

Editorial information provided by DB-Engines

Name

Description

AI-powered hosted search, recommendation and personalization platform providing tools for both low-code and full-code development

Cloud-hosted realtime document store. iOS, Android, and JavaScript clients share one Realtime Database instance and automatically receive updates with the newest data.

Embeddable relational database for web apps written in pure JavaScript

TimeSeries DBMS for AIoT and BigData

Cloud-based data warehousing service for structured and semi-structured data

Primary database model

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

Score	2.11
Rank	#118	Overall
	#11	Search engines

Score	13.64
Rank	#39	Overall
	#6	Document stores

Score	0.33
Rank	#286	Overall
	#131	Relational DBMS

Score	0.17
Rank	#337	Overall
	#30	Time Series DBMS

Score	130.36
Rank	#8	Overall
	#5	Relational DBMS

Website

www.coveo.com

firebase.google.com/products/realtime-database

google.github.io/lovefield

machbase.com

www.snowflake.com

Technical documentation

docs.coveo.com

firebase.google.com/docs/database

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

machbase.com/dbms

docs.snowflake.net/manuals/index.html

Developer

Coveo

Google

acquired by Google 2014

Google

Machbase

Snowflake Computing Inc.

Initial release

2012

2014

2013

2014

Current release

2.1.12, February 2017

V8.0, August 2023

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

free test version available

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

JavaScript

Server operating systems

hosted

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

tested with Chrome, Firefox, IE, Safari

Linux
macOS
Windows

hosted

Data scheme

hybrid - fields need to be configured prior to indexing, but relationships can be exploited at query time without pre-configuration

schema-free

yes

support of semi-structured data formats (JSON, XML, Avro)

Typing

predefined data types such as float or date

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.

yes

Secondary indexes

yes

SQL

Support of SQL

SQL-like query language

via JavaScript builder pattern

SQL-like query language

yes

APIs and other access methods

RESTful HTTP API

Android
iOS
JavaScript API
RESTful HTTP API

gRPC
HTTP REST
JDBC
MQTT (Message Queue Telemetry Transport)
ODBC

CLI Client
JDBC
ODBC

Supported programming languages

C#
Java
JavaScript
Python

Java
JavaScript
Objective-C

JavaScript

C
C#
C++
Go
Java
JavaScript
PHP

via ODBC
Python
R

via ODBC
Scala

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

Triggers

yes

Callbacks are triggered when data changes

Using read-only observers

similar concept for controling cloud resources

Partitioning methods

Methods for storing different data on different nodes

yes

none

Sharding

yes

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

selectable replication factor

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

if the client is offline
Immediate Consistency

if the client is online

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

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

yes

volatile and lookup table

User concepts

Access control

granular access controls, API key management, content filters

yes, based on authentication and database rules

simple password-based access control

Users with fine-grained authorization concept, user roles and pluggable 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.