DBMS > Coveo vs. Drizzle vs. Google Cloud Firestore vs. Tkrzw

System Properties Comparison Coveo vs. Drizzle vs. Google Cloud Firestore vs. Tkrzw

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

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

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

Cloud Firestore is an auto-scaling document database for storing, syncing, and querying data for mobile and web apps. It offers seamless integration with other Firebase and Google Cloud Platform products.

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

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

Score	2.28
Rank	#114	Overall
	#11	Search engines

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores

Website

www.coveo.com

firebase.google.com/products/firestore

dbmx.net/tkrzw

Technical documentation

docs.coveo.com

firebase.google.com/docs/firestore

Developer

Coveo

Drizzle project, originally started by Brian Aker

Google

Mikio Hirabayashi

Initial release

2012

2008

2017

2020

Current release

7.2.4, September 2012

0.9.3, August 2020

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

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

C++

Server operating systems

hosted

FreeBSD
Linux
OS X

hosted

Linux
macOS

Data scheme

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

yes

schema-free

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.

Secondary indexes

yes

SQL

Support of SQL

yes

with proprietary extensions

APIs and other access methods

RESTful HTTP API

JDBC

Android
gRPC (using protocol buffers) API
iOS
JavaScript API
RESTful HTTP API

Supported programming languages

C#
Java
JavaScript
Python

C
C++
Java
PHP

Go
Java
JavaScript
JavaScript (Node.js)
Objective-C
Python

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

Triggers

yes

hooks for callbacks inside the server can be used.

yes, with Cloud Functions

Partitioning methods

Methods for storing different data on different nodes

yes

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

ACID

yes

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

using specific database classes

User concepts

Access control

granular access controls, API key management, content filters

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Access rights for users, groups and roles based on Google Cloud Identity and Access Management. Security Rules for 3rd party authentication using Firebase Auth.

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

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Cloud-based DBMS's popularity grows at high rates
12 December 2019, Paul Andlinger

show all

Recent citations in the news

Coveo Debuts GenAI Tools on Genesys Cloud and AppFoundry
17 May 2024, CX Today

Coveo Named a Leader in the 2024 Gartner® Magic Quadrant™ for Search and Product Discovery
16 May 2024, PR Newswire

Coveo expands partnership with Genesys to empower contact center agents with various types of AI
16 May 2024, KMWorld Magazine

Coveo announced new partnership with Genesys
16 May 2024, Martechcube

Coveo Recognized as a Leader in Gartner's 2014 Magic Quadrant for Enterprise Search
17 May 2024, Yahoo Eurosport UK

provided by Google News

Google's AI-First Strategy Brings Vector Support To Cloud Databases
1 March 2024, Forbes

Realtime vs Cloud Firestore: Which Firebase Database to go?
8 March 2024, Appinventiv

Google's Cloud Firestore is now generally available
31 January 2019, ZDNet

Google launches Cloud Firestore, a new document database for app developers
3 October 2017, TechCrunch

Google's Cloud-Native NoSQL Database Cloud Firestore Is Now Generally Available
8 February 2019, InfoQ.com

provided by Google News

Share this page