DBMS > Firebase Realtime Database vs. Manticore Search vs. Snowflake vs. SpatiaLite

System Properties Comparison Firebase Realtime Database vs. Manticore Search vs. Snowflake vs. SpatiaLite

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

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

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

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

Spatial extension of SQLite

Primary database model

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

Relational DBMS

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

Score	14.29
Rank	#39	Overall
	#6	Document stores

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	121.33
Rank	#9	Overall
	#6	Relational DBMS

Score	1.60
Rank	#149	Overall
	#3	Spatial DBMS

Website

firebase.google.com/products/realtime-database

manticoresearch.com

www.snowflake.com

www.gaia-gis.it/fossil/libspatialite/index

Technical documentation

firebase.google.com/docs/database

manual.manticoresearch.com

docs.snowflake.net/manuals/index.html

www.gaia-gis.it/gaia-sins/spatialite_topics.html

Developer

Google

acquired by Google 2014

Manticore Software

Snowflake Computing Inc.

Alessandro Furieri

Initial release

2012

2017

2014

2008

Current release

6.0, February 2023

5.0.0, August 2020

License

Commercial or Open Source

commercial

Open Source

GPL version 2

commercial

Open Source

MPL 1.1, GPL v2.0 or LGPL v2.1

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

hosted

server-less

Data scheme

schema-free

Fixed schema

yes

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

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

yes

APIs and other access methods

Android
iOS
JavaScript API
RESTful HTTP API

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

CLI Client
JDBC
ODBC

Supported programming languages

Java
JavaScript
Objective-C

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

JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

limited functionality with using 'rules'

user defined functions

Triggers

Callbacks are triggered when data changes

similar concept for controling cloud resources

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

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

yes

none

Replication methods

Methods for redundantly storing data on multiple nodes

Synchronous replication based on Galera library

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

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

isolated transactions for atomic changes and binary logging for safe writes

ACID

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.

yes

User concepts

Access control

yes, based on authentication and database rules

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.