DBMS > Atos Standard Common Repository vs. MarkLogic vs. RDF4J vs. Yaacomo

System Properties Comparison Atos Standard Common Repository vs. MarkLogic vs. RDF4J vs. Yaacomo

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.

Yaacomo seems to be discontinued and is removed from the DB-Engines ranking

Description

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

Operational and transactional Enterprise NoSQL database

RDF4J is a Java framework for processing RDF data, supporting both memory-based and a disk-based storage.

OpenCL based in-memory RDBMS, designed for efficiently utilizing the hardware via parallel computing

Primary database model

Document store
Key-value store

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

RDF store

Relational DBMS

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.69
Rank	#230	Overall
	#9	RDF stores

Website

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

www.marklogic.com

rdf4j.org

yaacomo.com

Technical documentation

docs.marklogic.com

rdf4j.org/documentation

Developer

Atos Convergence Creators

MarkLogic Corp.

Since 2016 officially forked into an Eclipse project, former developer was Aduna Software.

Q2WEB GmbH

Initial release

2016

2001

2004

2009

Current release

1703

11.0, December 2022

License

Commercial or Open Source

commercial

restricted free version is available

Open Source

Eclipse Distribution License (EDL), v1.0.

commercial

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

Server operating systems

Linux

Linux
OS X
Windows

Linux
OS X
Unix
Windows

Android
Linux
Windows

Data scheme

Schema and schema-less with LDAP views

schema-free

Schema can be enforced

yes

RDF Schemas

yes

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

SQL92

yes

APIs and other access methods

LDAP

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

Java API
RIO

RDF Input/Output
Sail API
SeRQL

Sesame RDF Query Language
Sesame REST HTTP Protocol
SPARQL

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

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

Java
PHP
Python

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

yes

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

none

horizontal partitioning

Replication methods

Methods for redundantly storing data on multiple nodes

yes

none

Source-replica replication

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

ACID

Isolation support depends on the API used

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

in-memory storage is supported as well

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

yes

User concepts

Access control

LDAP bind authentication

Role-based access control at the document and subdocument levels

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

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
23 April 2024, Medium

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

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

Progress's $355m move for MarkLogic sets the tone for 2023
4 January 2023, The Stack

Progress to acquire PE-backed data platform MarkLogic for $355m
4 January 2023, PE Hub

provided by Google News

GraphDB Goes Open Source
27 January 2020, iProgrammer

Ontotext's GraphDB 8.10 Makes Knowledge Graph Experience Faster and Richer
13 June 2019, Markets Insider

provided by Google News

Share this page