DBMS > Atos Standard Common Repository vs. RavenDB vs. SQLite vs. TempoIQ

System Properties Comparison Atos Standard Common Repository vs. RavenDB vs. SQLite vs. TempoIQ

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.

TempoIQ seems to be decommissioned. It 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

Open Source Operational and Transactional Enterprise NoSQL Document Database

Widely used embeddable, in-process RDBMS

Scalable analytics DBMS for sensor data, provided as a service (SaaS)

Primary database model

Document store
Key-value store

Document store

Relational DBMS

Time Series DBMS

Secondary database models

Graph DBMS
Spatial DBMS
Time Series DBMS

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

Score	2.68
Rank	#102	Overall
	#19	Document stores

Score	103.35
Rank	#10	Overall
	#7	Relational DBMS

Website

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

ravendb.net

www.sqlite.org

tempoiq.com (offline)

Technical documentation

ravendb.net/docs

www.sqlite.org/docs.html

Developer

Atos Convergence Creators

Hibernating Rhinos

Dwayne Richard Hipp

TempoIQ

Initial release

2016

2010

2000

2012

Current release

1703

5.4, July 2022

3.46.1 (13 August 2024), August 2024

License

Commercial or Open Source

commercial

Open Source

AGPL version 3, commercial license available

Open Source

Public Domain

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

Server operating systems

Linux

Linux
macOS
Raspberry Pi
Windows

server-less

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 query language (RQL)

yes

SQL-92 is not fully supported

APIs and other access methods

LDAP

.NET Client API
F# Client API
Go Client API
Java Client API
NodeJS Client API
PHP Client API
Python Client API
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

HTTP API

Supported programming languages

All languages with LDAP bindings

.Net
C#
F#
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby

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

C#
Java
JavaScript

Node.js
Python
Ruby

Server-side scripts

Stored procedures

yes

Triggers

yes

Realtime Alerts

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Default ACID transactions on the local node (eventually consistent across the cluster). Atomic operations with cluster-wide ACID transactions. Eventual consistency for indexes and full-text search indexes.

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID, Cluster-wide transaction available

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

Authorization levels configured per client per database

simple authentication-based access control

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.