DBMS > Atos Standard Common Repository vs. Memcached vs. Spark SQL vs. SQLite vs. SurrealDB

System Properties Comparison Atos Standard Common Repository vs. Memcached vs. Spark SQL vs. SQLite vs. SurrealDB

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

In-memory key-value store, originally intended for caching

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

Widely used embeddable, in-process RDBMS

A fully ACID transactional, developer-friendly, multi-model DBMS

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Document store
Graph DBMS

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

Score	18.08
Rank	#32	Overall
	#4	Key-value stores

Score	18.04
Rank	#33	Overall
	#20	Relational DBMS

Score	111.41
Rank	#10	Overall
	#7	Relational DBMS

Score	1.02
Rank	#190	Overall
	#33	Document stores
	#18	Graph DBMS

Website

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

Technical documentation

github.com/memcached/memcached/wiki

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

www.sqlite.org/docs.html

surrealdb.com/docs

Developer

Atos Convergence Creators

Danga Interactive

originally developed by Brad Fitzpatrick for LiveJournal

Apache Software Foundation

Dwayne Richard Hipp

SurrealDB Ltd

Initial release

2016

2003

2014

2000

2022

Current release

1703

1.6.27, May 2024

3.5.0 ( 2.13), September 2023

3.46.0 (23 May 2024), May 2024

v1.5.0, May 2024

License

Commercial or Open Source

commercial

Open Source

BSD license

Open Source

Apache 2.0

Open Source

Public Domain

Open Source

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

Scala

Rust

Server operating systems

Linux

FreeBSD
Linux
OS X
Unix
Windows

Linux
OS X
Windows

server-less

Linux
macOS
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

dynamic column types

schema-free

Typing

predefined data types such as float or date

optional

yes

not rigid because of 'dynamic typing' concept.

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

SQL-like DML and DDL statements

yes

SQL-92 is not fully supported

SQL-like query language

APIs and other access methods

LDAP

Proprietary protocol

JDBC
ODBC

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GraphQL
RESTful HTTP API
WebSocket

Supported programming languages

All languages with LDAP bindings

.Net
C
C++
ColdFusion
Erlang
Java
Lisp
Lua
OCaml
Perl
PHP
Python
Ruby

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

Deno
Go
JavaScript (Node.js)
Rust

Server-side scripts

Stored procedures

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

yes, utilizing Spark Core

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Repcached, a Memcached patch, provides this functionallity

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

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

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

yes

using SASL (Simple Authentication and Security Layer) protocol

yes, based on authentication and database rules

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.