DBMS > Atos Standard Common Repository vs. Google Cloud Firestore vs. JaguarDB vs. Splunk

System Properties Comparison Atos Standard Common Repository vs. Google Cloud Firestore vs. JaguarDB vs. Splunk

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

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.

Performant, highly scalable DBMS for AI and IoT applications

Analytics Platform for Big Data

Primary database model

Document store
Key-value store

Document store

Key-value store
Vector DBMS

Search engine

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

Score	7.85
Rank	#51	Overall
	#8	Document stores

Score	0.00
Rank	#383	Overall
	#60	Key-value stores
	#13	Vector DBMS

Score	86.45
Rank	#14	Overall
	#2	Search engines

Website

atos.net/en/convergence-creators/portfolio/standard-common-repository

firebase.google.com/products/firestore

www.jaguardb.com

www.splunk.com

Technical documentation

firebase.google.com/docs/firestore

www.jaguardb.com/support.html

docs.splunk.com/Documentation/Splunk

Developer

Atos Convergence Creators

Google

DataJaguar, Inc.

Splunk Inc.

Initial release

2016

2017

2015

2003

Current release

1703

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

GPL V3.0

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

Java

C++

the server part. Clients available in other languages

Server operating systems

Linux

hosted

Linux

Linux
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

Typing

predefined data types such as float or date

optional

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

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

Splunk Search Processing Language for search commands

APIs and other access methods

LDAP

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

JDBC
ODBC

HTTP REST

Supported programming languages

All languages with LDAP bindings

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

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

C#
Java
JavaScript
PHP
Python
Ruby

Server-side scripts

Stored procedures

yes, Firebase Rules & Cloud Functions

yes

Triggers

yes

yes, with Cloud Functions

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

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 or Eventual Consistency depending on configuration

Immediate Consistency

Eventual Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

yes

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

In-memory capabilities

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

yes

User concepts

Access control

LDAP bind authentication

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

rights management via user accounts

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

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

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

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

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

Google’s Firebase gets AI extensions, opens up its marketplace
10 May 2023, TechCrunch

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

provided by Google News

Share this page