DBMS > Atos Standard Common Repository vs. DataFS vs. GeoMesa vs. Sqrrl

System Properties Comparison Atos Standard Common Repository vs. DataFS vs. GeoMesa vs. Sqrrl

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.

Sqrrl has been acquired by Amazon and became a part of Amazon Web Services. It has been removed from the DB-Engines ranking.

Description

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

All data is stored inside objects which are linked by so-called link attributes. Objects consist of classes which can be extended and de-extended at runtime. Graphs can be defined with a struct.

GeoMesa is a distributed spatio-temporal DBMS based on various systems as storage layer.

Adaptable, secure NoSQL built on Apache Accumulo

Primary database model

Document store
Key-value store

Object oriented DBMS

Spatial DBMS

Document store
Graph DBMS
Key-value store
Wide column store

Secondary database models

Graph DBMS

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

Score	0.06
Rank	#354	Overall
	#15	Object oriented DBMS

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Website

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

newdatabase.com

www.geomesa.org

sqrrl.com

Technical documentation

dev.mobiland.com/Overview.xsp

www.geomesa.org/documentation/stable/user/index.html

Developer

Atos Convergence Creators

Mobiland AG

CCRi and others

Amazon

originally Sqrrl Data, Inc.

Initial release

2016

2018

2014

2012

Current release

1703

1.1.263, October 2022

4.0.5, February 2024

License

Commercial or Open Source

commercial

Open Source

Apache License 2.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

Scala

Java

Server operating systems

Linux

Windows

Linux

Data scheme

Schema and schema-less with LDAP views

Classes, Structs, and Lists are written in proprietary DataTypeDefinitionLanguage (.dtdl) and Objects consisting of those are written in proprietary DataAccessDefinitionLanguage (.dadl)

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

APIs and other access methods

LDAP

.NET Client API
Proprietary client DLL
WinRT client

Accumulo Shell
Java API
JDBC
ODBC
RESTful HTTP API
Thrift

Supported programming languages

All languages with LDAP bindings

.Net
C
C#
C++
VB.Net

Actionscript
C

using GLib
C#
C++
Cocoa
Delphi
Erlang
Go
Haskell
Java
JavaScript
OCaml
Perl
PHP
Python
Ruby
Smalltalk

Server-side scripts

Stored procedures

Triggers

yes

no, except callback-events from server when changes happened

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

Proprietary Sharding system

depending on storage layer

Sharding

making use of Hadoop

Replication methods

Methods for redundantly storing data on multiple nodes

yes

depending on storage layer

selectable replication factor

making use of Hadoop

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

depending on storage layer

Immediate Consistency

Document store kept consistent with combination of global timestamping, row-level transactions, and server-side consistency resolution.

Foreign keys

Referential integrity

yes

Transaction concepts

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

Atomic execution of specific operations

ACID

Atomic updates per row, document, or graph entity

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

depending on storage layer

User concepts

Access control

LDAP bind authentication

Windows-Profile

yes

depending on the DBMS used for storage

Cell-level Security, Data-Centric Security, Role-Based Access Control (RBAC), Attribute-Based Access Control (ABAC)

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

Spatial database management systems
6 April 2021, Matthias Gelbmann

show all

Recent citations in the news

Splunk details Sqrrl 'screw-ups' that hampered threat hunting
6 May 2024, TechTarget

Amazon acquires cybersecurity startup Sqrrl
8 June 2023, cisomag.com

Millennials possess the advantage of time for wealth creation, says Yashoraj Tyagi of Sqrrl | Mint
18 September 2023, Mint

Amazon's cloud business acquires Sqrrl, a security start-up with NSA roots
23 January 2018, CNBC

AWS beefs up threat detection with Sqrrl acquisition
24 January 2018, TechCrunch

provided by Google News

Share this page