DBMS > Atos Standard Common Repository vs. Drizzle vs. Ehcache vs. Linter vs. SWC-DB

System Properties Comparison Atos Standard Common Repository vs. Drizzle vs. Ehcache vs. Linter vs. SWC-DB

Editorial information provided by DB-Engines

Name

This system has been discontinued and will be removed from the DB-Engines ranking.

Drizzle has published its last release in September 2012. The open-source project is discontinued and Drizzle is excluded from the DB-Engines ranking.

Description

Highly scalable database system, designed for managing session and subscriber data in modern mobile communication networks

MySQL fork with a pluggable micro-kernel and with an emphasis of performance over compatibility.

A widely adopted Java cache with tiered storage options

RDBMS for high security requirements

A high performance, scalable Wide Column DBMS

Primary database model

Document store
Key-value store

Secondary database models

Spatial DBMS

Time Series DBMS

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	0.09
Rank	#346	Overall
	#152	Relational DBMS

Score	0.01
Rank	#376	Overall
	#13	Wide column stores

Website

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

www.ehcache.org

linter.ru

github.com/kashirin-alex/swc-db
www.swcdb.org

Technical documentation

www.ehcache.org/documentation

Developer

Atos Convergence Creators

Drizzle project, originally started by Brian Aker

Terracotta Inc, owned by Software AG

relex.ru

Alex Kashirin

Initial release

2016

2008

2009

1990

2020

Current release

1703

7.2.4, September 2012

3.10.0, March 2022

0.5, April 2021

License

Commercial or Open Source

commercial

Open Source

GNU GPL

Open Source

Apache Version 2; commercial licenses available

commercial

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

Java

C and C++

C++

Server operating systems

Linux

FreeBSD
Linux
OS X

All OS with a Java VM

AIX
Android
BSD
HP Open VMS
iOS
Linux
OS X
VxWorks
Windows

Linux

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

yes

schema-free

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

SQL

Support of SQL

yes

with proprietary extensions

yes

SQL-like query language

APIs and other access methods

LDAP

JDBC

JCache

ADO.NET
JDBC
LINQ
ODBC
OLE DB
Oracle Call Interface (OCI)

Proprietary protocol
Thrift

Supported programming languages

All languages with LDAP bindings

C
C++
Java
PHP

Java

C
C#
C++
Java
Perl
PHP
Python
Qt
Ruby
Tcl

C++

Server-side scripts

Stored procedures

yes

proprietary syntax with the possibility to convert from PL/SQL

Triggers

yes

hooks for callbacks inside the server can be used.

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

by using Terracotta Server

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication
Source-replica replication

yes

by using Terracotta Server

Source-replica replication

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

Tunable Consistency (Strong, Eventual, Weak)

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

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

Pluggable authentication mechanisms

e.g. LDAP, HTTP

fine grained access rights according to SQL-standard

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.

Related products and services

We invite representatives of vendors of related products to contact us for presenting information about their offerings here.

More resources

DB-Engines blog posts

MySQL won the April ranking; did its forks follow?
1 April 2015, Paul Andlinger

Has MySQL finally lost its mojo?
1 July 2013, Matthias Gelbmann

show all

Recent citations in the news

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, DZone

provided by Google News

СУБД «Линтер Бастион» прошла сертификацию ФСТЭК России по новым требованиям к системам управления ...
11 March 2024, ServerNews

provided by Google News

2022 All O-Zone Football Team
17 December 2022, Ozarks Sports Zone

provided by Google News

Share this page