DBMS > Atos Standard Common Repository vs. Derby vs. Geode vs. JaguarDB

System Properties Comparison Atos Standard Common Repository vs. Derby vs. Geode vs. JaguarDB

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

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

Full-featured RDBMS with a small footprint, either embedded into a Java application or used as a database server.

Geode is a distributed data container, pooling memory, CPU, network resources, and optionally local disk across multiple processes

Performant, highly scalable DBMS for AI and IoT applications

Primary database model

Document store
Key-value store

Relational DBMS

Key-value store

Key-value store
Vector DBMS

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

Score	5.30
Rank	#66	Overall
	#36	Relational DBMS

Score	1.99
Rank	#133	Overall
	#23	Key-value stores

Score	0.09
Rank	#356	Overall
	#53	Key-value stores
	#13	Vector DBMS

Website

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

db.apache.org/derby

geode.apache.org

www.jaguardb.com

Technical documentation

db.apache.org/derby/manuals/index.html

geode.apache.org/docs

www.jaguardb.com/support.html

Developer

Atos Convergence Creators

Apache Software Foundation

Originally developed by Gemstone. They outsourced the project to Apache in 2015 but still deliver a commercial version as Gemfire.

DataJaguar, Inc.

Initial release

2016

1997

2002

2015

Current release

1703

10.17.1.0, November 2023

1.1, February 2017

3.3 July 2023

License

Commercial or Open Source

commercial

Open Source

Apache version 2

Open Source

Apache Version 2; commercial licenses available as Gemfire

Open Source

GPL V3.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

Server operating systems

Linux

All OS with a Java VM

the JDK (8 or later) is also required

Linux

Data scheme

Schema and schema-less with LDAP views

yes

schema-free

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

SQL-like query language (OQL)

A subset of ANSI SQL is implemented

but no views, foreign keys, triggers

APIs and other access methods

LDAP

JDBC

Java Client API
Memcached protocol
RESTful HTTP API

JDBC
ODBC

Supported programming languages

All languages with LDAP bindings

Java

.Net
All JVM based languages
C++
Groovy
Java
Scala

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

Server-side scripts

Stored procedures

Java Stored Procedures

user defined functions

Triggers

yes

Cache Event Listeners

Partitioning methods

Methods for storing different data on different nodes

Sharding

cell division

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

Source-replica replication

Multi-source replication

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Immediate Consistency or Eventual Consistency depending on configuration

Immediate Consistency

Eventual 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

yes, on a single node

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

User concepts

Access control

LDAP bind authentication

fine grained access rights according to SQL-standard

Access rights per client and object definable

rights management via user accounts

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

JDBC tutorial: Easy installation and setup with Apache Derby
20 December 2019, TheServerSide.com

Top Database Tools for Java Developers in 2023
17 November 2023, TechRepublic

Installing Apache Hive 3.1.2 on Windows 10 | by Hadi Fadlallah
3 May 2020, Towards Data Science

The Arrival of Java 20
21 March 2023, blogs.oracle.com

The Ultimate Open Source Database List Profiling 16 Software Tools
30 May 2019, Solutions Review

provided by Google News

This is how much one of the most expensive gems costs at the Tucson gem show
11 February 2024, KGUN 9 Tucson News

Apache Geode Spawns 'All Sorts of In-Memory Things'
4 January 2017, The New Stack

Where Does Apache Geode Fit in CQRS Architectures?
18 December 2016, InfoQ.com

1. Introduction to Pivotal GemFire In-Memory Data Grid and Apache Geode - Scaling Data Services with Pivotal ...
15 November 2018, oreilly.com

Event-Driven Architectures with Apache Geode and Spring Integration
20 March 2019, InfoQ.com

provided by Google News

Share this page