DBMS > Ehcache vs. GeoMesa vs. MarkLogic vs. VelocityDB vs. YTsaurus

System Properties Comparison Ehcache vs. GeoMesa vs. MarkLogic vs. VelocityDB vs. YTsaurus

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

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

Operational and transactional Enterprise NoSQL database

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

YTsaurus is an open source platform for distributed storage and processing.

Primary database model

Key-value store

Spatial DBMS

Document store
Native XML DBMS
RDF store

as of version 7
Search engine

Graph DBMS
Object oriented DBMS

Document store
Key-value store

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

Score	4.64
Rank	#68	Overall
	#8	Key-value stores

Score	0.86
Rank	#205	Overall
	#4	Spatial DBMS

Score	5.18
Rank	#63	Overall
	#11	Document stores
	#1	Native XML DBMS
	#1	RDF stores
	#7	Search engines

Score	0.11
Rank	#354	Overall
	#37	Graph DBMS
	#15	Object oriented DBMS

Score	0.21
Rank	#324	Overall
	#45	Document stores
	#48	Key-value stores

Website

Technical documentation

www.ehcache.org/documentation

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

docs.marklogic.com

velocitydb.com/UserGuide

ytsaurus.tech/docs/en

Developer

Terracotta Inc, owned by Software AG

CCRi and others

MarkLogic Corp.

VelocityDB Inc

Yandex

Initial release

2009

2014

2001

2011

2023

Current release

3.10.0, March 2022

5.0.0, May 2024

11.0, December 2022

7.x

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache License 2.0

commercial

restricted free version is available

commercial

Open Source

Apache License, 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

Scala

C++

Server operating systems

All OS with a Java VM

Linux
OS X
Windows

Any that supports .NET

Ubuntu

Data scheme

schema-free

yes

schema-free

Schema can be enforced

yes

Typing

predefined data types such as float or date

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

SQL92

YQL, an SQL-based language, is supported

APIs and other access methods

JCache

Java API
Node.js Client API
ODBC
proprietary Optic API

Proprietary Query API, introduced with version 9
RESTful HTTP API
SPARQL
WebDAV
XDBC
XQuery
XSLT

.Net

Supported programming languages

Java

C
C#
C++
Java
JavaScript (Node.js)
Perl
PHP
Python
Ruby

.Net

C++
Go
Java
JavaScript
Python

Server-side scripts

Stored procedures

yes

via XQuery or JavaScript

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

depending on storage layer

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

depending on storage layer

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

via Hadoop Connector, HDFS Direct Access and in-database MapReduce jobs

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

depending on storage layer

Immediate Consistency

Foreign keys

Referential integrity

Transaction concepts

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

yes

supports JTA and can work as an XA resource

ACID

can act as a resource manager in an XA/JTA transaction

ACID

Concurrency

Support for concurrent manipulation of data

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

depending on storage layer

yes, with Range Indexes

yes

User concepts

Access control

yes

depending on the DBMS used for storage

Role-based access control at the document and subdocument levels

Based on Windows Authentication

Access Control Lists

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

Scaling Australia's Most Popular Online News Sites with Ehcache
6 December 2010, InfoQ.com

Atlassian asks customers to patch critical Jira vulnerability
22 July 2021, BleepingComputer

Critical Jira Flaw in Atlassian Could Lead to RCE
22 July 2021, Threatpost

DZone Coding Java JBoss 5 to 7 in 11 steps
9 January 2014, DZone

provided by Google News

Vantage Closes Wholesale Deal in Santa Clara
30 May 2024, Data Center Knowledge

MarkLogic “The NoSQL Database”. In the MarkLogic Query Console, you can… | by Abhay Srivastava | Apr, 2024
22 April 2024, Medium

Database Platform to Simplify Complex Data | Progress Marklogic
7 February 2023, Progress Software

Intelligence for multi-domain warfighters can now be sourced from logistics operations
13 May 2024, Breaking Defense

ABN AMRO Moves Progress-Powered Credit Store App to Azure Cloud; Achieves 40% Faster Data Processing, Lower ...
12 March 2024, GlobeNewswire

provided by Google News

Share this page