DBMS > Ehcache vs. GeoMesa vs. Heroic vs. SQLite vs. Weaviate

System Properties Comparison Ehcache vs. GeoMesa vs. Heroic vs. SQLite vs. Weaviate

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.

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

Widely used embeddable, in-process RDBMS

An AI-native realtime vector database engine that integrates scalable machine learning models.

Primary database model

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

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

Score	0.78
Rank	#213	Overall
	#4	Spatial DBMS

Score	0.51
Rank	#255	Overall
	#21	Time Series DBMS

Score	114.32
Rank	#10	Overall
	#7	Relational DBMS

Score	1.73
Rank	#143	Overall
	#5	Vector DBMS

Website

www.ehcache.org

www.geomesa.org

github.com/spotify/heroic

www.sqlite.org

github.com/weaviate/weaviate
weaviate.io

Technical documentation

www.ehcache.org/documentation

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

spotify.github.io/heroic

www.sqlite.org/docs.html

weaviate.io/developers/weaviate

Developer

Terracotta Inc, owned by Software AG

CCRi and others

Spotify

Dwayne Richard Hipp

Weaviate B.V.

Initial release

2009

2014

2000

2019

Current release

3.10.0, March 2022

4.0.5, February 2024

3.45.3 (15 April 2024), April 2024

1.19, May 2023

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

Apache License 2.0

Open Source

Apache 2.0

Open Source

Public Domain

Open Source

commercial license available with Weaviate Enterprise

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

All OS with a Java VM

server-less

Data scheme

schema-free

yes

schema-free

yes

dynamic column types

yes, maps to GraphQL interface

Typing

predefined data types such as float or date

yes

not rigid because of 'dynamic typing' concept.

yes

string, int, float, geo point, date, cross reference, fuzzy references

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

all data objects are indexed in a semantic vector space (the Contextionary), all primitive fields are indexed

SQL

Support of SQL

yes

SQL-92 is not fully supported

GraphQL is used as query language

APIs and other access methods

JCache

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

ADO.NET

inofficial driver
JDBC

inofficial driver
ODBC

inofficial driver

GraphQL query language
RESTful HTTP/JSON API

Supported programming languages

Java

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

JavaScript / TypeScript
Python

Server-side scripts

Stored procedures

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

depending on storage layer

Sharding

none

Sharding

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

depending on storage layer

yes

none

yes

MapReduce

Offers an API for user-defined Map/Reduce methods

yes

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

depending on storage layer

Eventual Consistency
Immediate Consistency

Eventual 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

depending on storage layer

yes

User concepts

Access control

yes

depending on the DBMS used for storage

API Keys
OpenID Connect Discovery

More information provided by the system vendor

Specific characteristics

Weaviate is an open source vector database that is robust, scalable, cloud-native,...
» more

Competitive advantages

Flexible deployment - Free, open source or fully-managed cloud vector database service...
» more

Typical application scenarios

As a database supporting the development of generative AI and semantic search applications...
» more

Key customers

All companies that have data.
» more

Market metrics

As of mid 2023: Over 2 million open source downloads 3500+ Weaviate Slack community...
» more

Licensing and pricing models

Weaviate is open-source, and free to use. Weaviate is also available as a fully managed...
» more

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.