DBMS > Atos Standard Common Repository vs. EXASOL vs. Google BigQuery vs. SpatiaLite vs. Sphinx

System Properties Comparison Atos Standard Common Repository vs. EXASOL vs. Google BigQuery vs. SpatiaLite vs. Sphinx

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

High-performance, in-memory, MPP database specifically designed for in-memory analytics.

Large scale data warehouse service with append-only tables

Spatial extension of SQLite

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

Primary database model

Document store
Key-value store

Relational DBMS

Spatial DBMS

Search engine

Secondary database models

Relational DBMS

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

Score	1.76
Rank	#139	Overall
	#62	Relational DBMS

Score	58.10
Rank	#19	Overall
	#13	Relational DBMS

Score	1.63
Rank	#146	Overall
	#3	Spatial DBMS

Score	5.95
Rank	#55	Overall
	#5	Search engines

Website

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

www.exasol.com

cloud.google.com/bigquery

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

sphinxsearch.com

Technical documentation

www.exasol.com/resources

cloud.google.com/bigquery/docs

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

sphinxsearch.com/docs

Developer

Atos Convergence Creators

Exasol

Google

Alessandro Furieri

Sphinx Technologies Inc.

Initial release

2016

2000

2010

2008

2001

Current release

1703

5.0.0, August 2020

3.5.1, February 2023

License

Commercial or Open Source

commercial

Open Source

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

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

Java

C++

Server operating systems

Linux

hosted

server-less

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

Data scheme

Schema and schema-less with LDAP views

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

full-text index on all search fields

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

APIs and other access methods

LDAP

.Net
JDBC
ODBC
WebSocket

RESTful HTTP/JSON API

Proprietary protocol

Supported programming languages

All languages with LDAP bindings

Java
Lua
Python
R

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

Server-side scripts

Stored procedures

user defined functions

in JavaScript

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Sharding

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

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Hadoop integration

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Since BigQuery is designed for querying data

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

LDAP bind authentication

Access rights for users, groups and roles according to SQL-standard

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.