DBMS > Atos Standard Common Repository vs. Google BigQuery vs. Manticore Search vs. SQream DB

System Properties Comparison Atos Standard Common Repository vs. Google BigQuery vs. Manticore Search vs. SQream DB

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

Large scale data warehouse service with append-only tables

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

a GPU-based, columnar RDBMS for big data analytics workloads

Primary database model

Document store
Key-value store

Relational DBMS

Search engine

Relational DBMS

Secondary database models

Time Series DBMS

using the Manticore Columnar Library

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	0.22
Rank	#312	Overall
	#21	Search engines

Score	0.70
Rank	#227	Overall
	#104	Relational DBMS

Website

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

cloud.google.com/bigquery

manticoresearch.com

sqream.com

Technical documentation

cloud.google.com/bigquery/docs

manual.manticoresearch.com

docs.sqream.com

Developer

Atos Convergence Creators

Google

Manticore Software

SQream Technologies

Initial release

2016

2010

2017

Current release

1703

6.0, February 2023

2022.1.6, December 2022

License

Commercial or Open Source

commercial

Open Source

GPL version 2

commercial

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++

C++, CUDA, Haskell, Java, Scala

Server operating systems

Linux

hosted

FreeBSD
Linux
macOS
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

yes

Fixed schema

yes

Typing

predefined data types such as float or date

optional

yes

Int, Bigint, Float, Timestamp, Bit, Int array, Bigint array, JSON, Boolean

yes, ANSI Standard SQL Types

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

Can index from XML

Secondary indexes

yes

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language

yes

APIs and other access methods

LDAP

RESTful HTTP/JSON API

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

.Net
JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

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

C++
Java
JavaScript (Node.js)
Python

Server-side scripts

Stored procedures

user defined functions

in JavaScript

user defined functions

user defined functions in Python

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

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

horizontal and vertical partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Synchronous replication based on Galera library

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

Since BigQuery is designed for querying 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

LDAP bind authentication

Access privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

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.