DBMS > Apache Drill vs. Atos Standard Common Repository vs. JaguarDB vs. Newts vs. SiteWhere

System Properties Comparison Apache Drill vs. Atos Standard Common Repository vs. JaguarDB vs. Newts vs. SiteWhere

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

Performant, highly scalable DBMS for AI and IoT applications

Time Series DBMS based on Cassandra

M2M integration platform for persisting/querying time series data

Primary database model

Document store
Relational DBMS

Document store
Key-value store

Key-value store
Vector DBMS

Time Series DBMS

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

Score	2.02
Rank	#124	Overall
	#22	Document stores
	#59	Relational DBMS

Score	0.06
Rank	#381	Overall
	#59	Key-value stores
	#13	Vector DBMS

Score	0.07
Rank	#375	Overall
	#41	Time Series DBMS

Score	0.06
Rank	#383	Overall
	#43	Time Series DBMS

Website

drill.apache.org

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

www.jaguardb.com

opennms.github.io/newts

github.com/sitewhere/sitewhere

Technical documentation

drill.apache.org/docs

www.jaguardb.com/support.html

github.com/OpenNMS/newts/wiki

sitewhere1.sitewhere.io/index.html

Developer

Apache Software Foundation

Atos Convergence Creators

DataJaguar, Inc.

OpenNMS Group

SiteWhere

Initial release

2012

2016

2015

2014

2010

Current release

1.20.3, January 2023

1703

3.3 July 2023

License

Commercial or Open Source

Open Source

Apache Version 2

commercial

Open Source

GPL V3.0

Open Source

Apache 2.0

Open Source

Common Public Attribution License Version 1.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++

the server part. Clients available in other languages

Java

Server operating systems

Linux
OS X
Windows

Linux

Linux
OS X
Windows

Data scheme

schema-free

Schema and schema-less with LDAP views

yes

schema-free

predefined scheme

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

Secondary indexes

yes

SQL

Support of SQL

SQL SELECT statement is SQL:2003 compliant

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

JDBC
ODBC
RESTful HTTP API

LDAP

JDBC
ODBC

HTTP REST
Java API

HTTP REST

Supported programming languages

C++

All languages with LDAP bindings

C
C++
Go
Java
JavaScript (Node.js)
PHP
Python
Ruby
Scala

Java

Server-side scripts

Stored procedures

user defined functions

Triggers

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Sharding

based on Cassandra

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Multi-source replication

selectable replication factor

based on Cassandra

selectable replication factor

based on HBase

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

Eventual Consistency

based on Cassandra
Immediate Consistency

based on Cassandra

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

Atomic execution of specific operations

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

User concepts

Access control

Depending on the underlying data source

LDAP bind authentication

rights management via user accounts

Users with fine-grained authorization concept

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

MapR to Speak on Stream Processing Systems, Apache Spark and Drill at Industry Events in January
31 May 2024, Yahoo Movies UK

Apache Drill vs. Apache Spark — Which SQL query engine is better for you?
23 September 2019, Towards Data Science

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

Apache Drill Poised to Crack Tough Data Challenges
19 May 2015, Datanami

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

provided by Google News

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

provided by Google News

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

Ten Popular IoT Platforms You Should be Aware of
27 March 2023, Open Source For You

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page