DBMS > Atos Standard Common Repository vs. Drizzle vs. MarkLogic vs. STSdb

System Properties Comparison Atos Standard Common Repository vs. Drizzle vs. MarkLogic vs. STSdb

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.

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.

Operational and transactional Enterprise NoSQL database

Key-Value Store with special method for indexing

optimized for high performance using a special indexing method

Primary database model

Document store
Key-value store

Relational DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Key-value store

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

Score	5.92
Rank	#58	Overall
	#10	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#6	Search engines

Score	0.04
Rank	#360	Overall
	#52	Key-value stores

Website

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

www.marklogic.com

github.com/STSSoft/STSdb4

Technical documentation

docs.marklogic.com

Developer

Atos Convergence Creators

Drizzle project, originally started by Brian Aker

MarkLogic Corp.

STS Soft SC

Initial release

2016

2008

2001

2011

Current release

1703

7.2.4, September 2012

11.0, December 2022

4.0.8, September 2015

License

Commercial or Open Source

commercial

Open Source

GNU GPL

commercial

restricted free version is available

Open Source

GPLv2, commercial license available

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

FreeBSD
Linux
OS X

Linux
OS X
Windows

Windows

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

Schema can be enforced

yes

Typing

predefined data types such as float or date

optional

yes

primitive types and user defined types (classes)

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

SQL92

APIs and other access methods

LDAP

JDBC

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

.NET Client API

Supported programming languages

All languages with LDAP bindings

C
C++
Java
PHP

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

C#
Java

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

Triggers

yes

hooks for callbacks inside the server can be used.

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

Multi-source replication
Source-replica replication

yes

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

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

can act as a resource manager in an XA/JTA transaction

Concurrency

Support for concurrent manipulation of data

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

yes, with Range Indexes

User concepts

Access control

LDAP bind authentication

Pluggable authentication mechanisms

e.g. LDAP, HTTP

Role-based access control at the document and subdocument levels

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

Infographic: What makes a Mobile Operator's setup future proof?
10 February 2024, Atos

provided by Google News

MarkLogic “The NoSQL Database”. In the MarkLogic Query Console, you can… | by Abhay Srivastava | Apr, 2024
22 April 2024, Medium

Database Platform to Simplify Complex Data | Progress Marklogic
7 February 2023, Progress Software

Intelligence for multi-domain warfighters can now be sourced from logistics operations
13 May 2024, Breaking Defense

ABN AMRO Moves Progress-Powered Credit Store App to Azure Cloud; Achieves 40% Faster Data Processing, Lower ...
12 March 2024, GlobeNewswire

Seven Quick Steps to Setting Up MarkLogic Server in Kubernetes
1 February 2024, release.nl

provided by Google News

Share this page