DBMS > Atos Standard Common Repository vs. Oracle Coherence vs. SQLite vs. Typesense

System Properties Comparison Atos Standard Common Repository vs. Oracle Coherence vs. SQLite vs. Typesense

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

Oracles in-memory data grid solution

Widely used embeddable, in-process RDBMS

A typo-tolerant, in-memory search engine optimized for instant search-as-you-type experiences and developer productivity

Primary database model

Document store
Key-value store

Key-value store

Relational DBMS

Search engine

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

Score	1.92
Rank	#130	Overall
	#22	Key-value stores

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.79
Rank	#210	Overall
	#14	Search engines

Website

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

www.oracle.com/java/coherence

www.sqlite.org

typesense.org

Technical documentation

docs.oracle.com/en/middleware/standalone/coherence

www.sqlite.org/docs.html

typesense.org/docs

Developer

Atos Convergence Creators

Oracle

Dwayne Richard Hipp

Initial release

2016

2007

2000

2015

Current release

1703

14.1, August 2023

3.45.3 (15 April 2024), April 2024

License

Commercial or Open Source

commercial

Open Source

Public Domain

Open Source

GPL V3

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

Server operating systems

Linux

All OS with a Java VM

server-less

Linux

Data scheme

Schema and schema-less with LDAP views

schema-free

yes

dynamic column types

schema-free

pre-defined schema optional

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

yes

SQL-92 is not fully supported

APIs and other access methods

LDAP

JCache
JPA
RESTful HTTP API

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

RESTful HTTP API

Supported programming languages

All languages with LDAP bindings

.Net
C++
Java

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

.Net

community maintained
Clojure

community maintained
Dart

community maintained
Go

community maintained
Java

community maintained
JavaScript
Perl

community maintained
PHP
Python
Ruby
Rust

community maintained
Swift

community maintained

Server-side scripts

Stored procedures

Triggers

yes

Live Events

yes

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

yes, with selectable consistency level

none

Multi-source replication using RAFT

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

configurable

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

optionally

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

authentification to access the cache via certificates or http basic authentication

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.