DBMS > Amazon DocumentDB vs. Google Cloud Firestore vs. Microsoft SQL Server vs. Sphinx

System Properties Comparison Amazon DocumentDB vs. Google Cloud Firestore vs. Microsoft SQL Server vs. Sphinx

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

Fast, scalable, highly available, and fully managed MongoDB-compatible database service

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.

Microsofts flagship relational DBMS

Open source search engine for searching in data from different sources, e.g. relational databases

Primary database model

Document store

Relational DBMS

Search engine

Secondary database models

Document store
Graph DBMS
Spatial DBMS

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

Score	1.91
Rank	#132	Overall
	#24	Document stores

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	824.29
Rank	#3	Overall
	#3	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Website

aws.amazon.com/documentdb

firebase.google.com/products/firestore

www.microsoft.com/en-us/sql-server

sphinxsearch.com

Technical documentation

aws.amazon.com/documentdb/resources

firebase.google.com/docs/firestore

learn.microsoft.com/en-US/sql/sql-server

sphinxsearch.com/docs

Developer

Google

Microsoft

Sphinx Technologies Inc.

Initial release

2019

2017

1989

2001

Current release

SQL Server 2022, November 2022

3.5.1, February 2023

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

GPL version 2, commercial licence 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

Linux
Windows

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

schema-free

yes

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

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

APIs and other access methods

proprietary protocol using JSON (MongoDB compatible)

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

ADO.NET
JDBC
ODBC
OLE DB
Tabular Data Stream (TDS)

Proprietary protocol

Supported programming languages

Go
Java
JavaScript (Node.js)
PHP
Python

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

C#
C++
Delphi
Go
Java
JavaScript (Node.js)
PHP
Python
R
Ruby
Visual Basic

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

Transact SQL, .NET languages, R, Python and (with SQL Server 2019) Java

Triggers

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

none

Sharding

tables can be distributed across several files (horizontal partitioning); sharding through federation

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

Multi-availability zones for high availability, asynchronous replication for up to 15 read replicas

Multi-source replication

yes, but depending on the SQL-Server Edition

none

MapReduce

Offers an API for user-defined Map/Reduce methods

may be implemented via Amazon Elastic MapReduce (Amazon EMR)

Using Cloud Dataflow

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency

Foreign keys

Referential integrity

typically not used, however similar functionality with DBRef possible

yes

Transaction concepts

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

Atomic single-document operations

yes

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 Sphinx index.

In-memory capabilities

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

yes

User concepts

Access control

Access rights for users and roles

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

fine grained access rights according to SQL-standard

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.