DBMS > Ehcache vs. Heroic vs. SAP Advantage Database Server vs. SQLite vs. VelocityDB

System Properties Comparison Ehcache vs. Heroic vs. SAP Advantage Database Server vs. SQLite vs. VelocityDB

Editorial information provided by DB-Engines

Name

SAP Advantage Database Server seems to be discontinued. Therefore it is excluded from the DB-Engines Ranking.

Description

A widely adopted Java cache with tiered storage options

Time Series DBMS built at Spotify based on Cassandra or Google Cloud Bigtable, and ElasticSearch

Low-cost RDBMS with access to ISAM and FoxPro data structures

Widely used embeddable, in-process RDBMS

A .NET Object Database that can be embedded/distributed and extended to a graph data model (VelocityGraph)

Primary database model

Key-value store

Time Series DBMS

Relational DBMS

Graph DBMS
Object oriented DBMS

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

Score	4.89
Rank	#67	Overall
	#8	Key-value stores

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	0.05
Rank	#358	Overall
	#36	Graph DBMS
	#16	Object oriented DBMS

Website

www.ehcache.org

github.com/spotify/heroic

www.sap.com/products/advantage-database-server.html

www.sqlite.org

velocitydb.com

Technical documentation

www.ehcache.org/documentation

spotify.github.io/heroic

www.sqlite.org/docs.html

velocitydb.com/UserGuide

Developer

Terracotta Inc, owned by Software AG

Spotify

Sybase, SAP

Dwayne Richard Hipp

VelocityDB Inc

Initial release

2009

2014

1993

2000

2011

Current release

3.10.0, March 2022

3.46.0 (23 May 2024), May 2024

7.x

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache 2.0

commercial

Open Source

Public Domain

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

Server operating systems

All OS with a Java VM

Linux
Windows

server-less

Any that supports .NET

Data scheme

schema-free

yes

dynamic column types

yes

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

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.

Secondary indexes

yes

via Elasticsearch

yes

SQL

Support of SQL

yes

SQL-92 is not fully supported

APIs and other access methods

JCache

HQL (Heroic Query Language, a JSON-based language)
HTTP API

.NET Client API
ADO.NET
JDBC
ODBC
OLE DB

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

.Net

Supported programming languages

Java

Delphi
Perl
PHP

Actionscript
Ada
Basic
C
C#
C++
D
Delphi
Forth
Fortran
Haskell
Java
JavaScript
Lisp
Lua
MatLab
Objective-C
OCaml
Perl
PHP
PL/SQL
Python
R
Ruby
Scala
Scheme
Smalltalk
Tcl

.Net

Server-side scripts

Stored procedures

yes

Triggers

yes

Cache Event Listeners

yes

Callbacks are triggered when data changes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

yes

Multi-source replication

CONFLICT Trigger to resolve replication conflicts
Source-replica replication

none

MapReduce

Offers an API for user-defined Map/Reduce methods

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Eventual Consistency
Immediate Consistency

Immediate Consistency

Foreign keys

Referential integrity

yes

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

Concurrency

Support for concurrent manipulation of data

yes

via file-system locks

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

In-memory capabilities

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

yes

caching of (temporary) tables can be configured

yes

User concepts

Access control

fine grained access rights according to SQL-standard

Based on Windows Authentication

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.