DBMS > Google Cloud Firestore vs. Manticore Search vs. Splunk

System Properties Comparison Google Cloud Firestore vs. Manticore Search vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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.

Multi-storage database for search, including full-text search.

Analytics Platform for Big Data

Primary database model

Document store

Search engine

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	8.96
Rank	#48	Overall
	#8	Document stores

Score	0.23
Rank	#317	Overall
	#21	Search engines

Score	88.71
Rank	#14	Overall
	#2	Search engines

Website

firebase.google.com/products/firestore

manticoresearch.com

www.splunk.com

Technical documentation

firebase.google.com/docs/firestore

manual.manticoresearch.com

docs.splunk.com/Documentation/Splunk

Developer

Google

Manticore Software

Splunk Inc.

Initial release

2017

2003

Current release

6.0, February 2023

License

Commercial or Open Source

commercial

Open Source

GPL version 2

commercial

Limited free edition and free developer edition available

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
macOS
Windows

Linux
OS X
Solaris
Windows

Data scheme

schema-free

Fixed schema

yes

Typing

predefined data types such as float or date

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, 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.

Can index from XML

yes

Secondary indexes

yes

full-text index on all search fields

yes

SQL

Support of SQL

SQL-like query language

Splunk Search Processing Language for search commands

APIs and other access methods

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

Binary API
RESTful HTTP/JSON API
RESTful HTTP/SQL API
SQL over MySQL

HTTP REST

Supported programming languages

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

Elixir
Go
Java
JavaScript (Node.js)
Perl
PHP
Python

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

user defined functions

yes

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-source replication

Synchronous replication based on Galera library

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Using Cloud Dataflow

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

isolated transactions for atomic changes and binary logging for safe writes

A 'Transaction' in Splunk has a different meaning: grouping related events into a single one for later searching

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

The original contents of fields are not stored in the Manticore index.

yes

In-memory capabilities

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

User concepts

Access control

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

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

DB-Engines blog posts

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

show all

Enterprise Search Engines almost double their popularity in the last 12 months
2 July 2014, Paul Andlinger

show all

Recent citations in the 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 Firebase gets AI extensions, opens up its marketplace
10 May 2023, TechCrunch

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

Firestore and Python | NoSQL on Google Cloud
7 August 2020, Towards Data Science

provided by Google News

Integrating Manticore Search with Apache Superset
8 August 2023, hackernoon.com

Comparing Meilisearch and Manticore Search Using Key Benchmarks
2 May 2023, hackernoon.com

Google's Gemini comes to databases
9 April 2024, Yahoo Canada Shine On

Clickhouse vs Elasticsearch vs Manticore Search Query Times With a 1.7B NYC Taxi Rides Benchmark
1 June 2022, hackernoon.com

8 Google Alternatives: How to Search Crypto, the Dark Web, More
1 February 2023, Gizmodo

provided by Google News

Share this page