DBMS > Apache Drill vs. Atos Standard Common Repository vs. Stardog vs. Tkrzw

System Properties Comparison Apache Drill vs. Atos Standard Common Repository vs. Stardog vs. Tkrzw

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

Schema-free SQL Query Engine for Hadoop, NoSQL and Cloud Storage

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

Enterprise Knowledge Graph platform and graph DBMS with high availability, high performance reasoning, and virtualization

A concept of libraries, allowing an application program to store and query key-value pairs in a file. Successor of Tokyo Cabinet and Kyoto Cabinet

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Graph DBMS
RDF store

Key-value store

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

Score	1.90
Rank	#126	Overall
	#23	Document stores
	#60	Relational DBMS

Score	1.93
Rank	#121	Overall
	#10	Graph DBMS
	#6	RDF stores

Score	0.00
Rank	#385	Overall
	#61	Key-value stores

Website

drill.apache.org

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

www.stardog.com

dbmx.net/tkrzw

Technical documentation

drill.apache.org/docs

docs.stardog.com

Developer

Apache Software Foundation

Atos Convergence Creators

Stardog-Union

Mikio Hirabayashi

Initial release

2012

2016

2010

2020

Current release

1.20.3, January 2023

1703

7.3.0, May 2020

0.9.3, August 2020

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

60-day fully-featured trial license; 1-year fully-featured non-commercial use license for academics/students

Open Source

Apache Version 2.0

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
OS X
Windows

Linux

Linux
macOS
Windows

Linux
macOS

Data scheme

schema-free

Schema and schema-less with LDAP views

schema-free and OWL/RDFS-schema support

schema-free

Typing

predefined data types such as float or date

yes

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

Import/export of XML data possible

Secondary indexes

yes

supports real-time indexing in full-text and geospatial

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

Yes, compatible with all major SQL variants through dedicated BI/SQL Server

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

LDAP

GraphQL query language
HTTP API
Jena RDF API
OWL
RDF4J API
Sesame REST HTTP Protocol
SNARL
SPARQL
Spring Data
Stardog Studio
TinkerPop 3

Supported programming languages

C++

All languages with LDAP bindings

.Net
Clojure
Groovy
Java
JavaScript
Python
Ruby

C++
Java
Python
Ruby

Server-side scripts

Stored procedures

user defined functions

user defined functions and aggregates, HTTP Server extensions in Java

Triggers

yes

via event handlers

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication in HA-Cluster

none

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

none

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency in HA-Cluster

Immediate Consistency

Foreign keys

Referential integrity

yes

relationships in graphs

Transaction concepts

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

Atomic execution of specific operations

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

Depending on the underlying data source

yes

In-memory capabilities

Is there an option to define some or all structures to be held in-memory only.

Depending on the underlying data source

yes

using specific database classes

User concepts

Access control

Depending on the underlying data source

LDAP bind authentication

Access rights for users and roles

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

Apache Drill case study: A tutorial on processing CSV files
9 June 2016, TheServerSide.com

Analyse Kafka messages with SQL queries using Apache Drill
27 September 2019, Towards Data Science

MapR Advances Support for Flexible and High Performance Analytics on JSON and S3 Data with Apache Drill
30 January 2019, Business Wire

Apache Drill Adds New Data Formats
28 March 2022, iProgrammer

Apache Drill Eliminates ETL, Data Transformation for MapR Database
11 April 2016, The New Stack

provided by Google News

Share this page