DBMS > Atos Standard Common Repository vs. Blueflood vs. ITTIA vs. Spark SQL vs. SQLite

System Properties Comparison Atos Standard Common Repository vs. Blueflood vs. ITTIA vs. Spark SQL vs. SQLite

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

Scalable TimeSeries DBMS based on Cassandra

Edge Time Series DBMS with Real-Time Stream Processing

Spark SQL is a component on top of 'Spark Core' for structured data processing

Widely used embeddable, in-process RDBMS

Primary database model

Document store
Key-value store

Time Series DBMS

Relational DBMS

Secondary database models

Relational DBMS

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

Score	0.06
Rank	#353	Overall
	#34	Time Series DBMS

Score	0.39
Rank	#273	Overall
	#24	Time Series DBMS

Score	18.96
Rank	#33	Overall
	#20	Relational DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Website

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

Technical documentation

github.com/rax-maas/blueflood/wiki

spark.apache.org/docs/latest/sql-programming-guide.html

www.sqlite.org/docs.html

Developer

Atos Convergence Creators

Rackspace

ITTIA L.L.C.

Apache Software Foundation

Dwayne Richard Hipp

Initial release

2016

2013

2007

2014

2000

Current release

1703

8.7

3.5.0 ( 2.13), September 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Apache 2.0

commercial

Open Source

Apache 2.0

Open Source

Public Domain

Cloud-based only

Only available as a cloud service

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C and C++

Scala

Server operating systems

Linux

Linux
OS X

Linux
Windows

Linux
OS X
Windows

server-less

Data scheme

Schema and schema-less with LDAP views

predefined scheme

Fixed schema

yes

dynamic column types

Typing

predefined data types such as float or date

optional

yes

Float/Blob/Integer/String/Unicode/Date/Time/Timestamp/Interval

yes

not rigid because of 'dynamic typing' concept.

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

yes

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

APIs and other access methods

LDAP

HTTP REST

JDBC
ODBC
RESTful HTTP API
WebSocket

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

Supported programming languages

All languages with LDAP bindings

C
C++
JavaScript (Node.js)
Python

Java
Python
R
Scala

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

Server-side scripts

Stored procedures

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

based on Cassandra

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

selectable replication factor

based on Cassandra

yes

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

yes

ACID

Concurrency

Support for concurrent manipulation of data

yes

yes, multi-version concurrency control (MVCC)

yes

via file-system locks

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

Database file passwords

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.