DBMS > Ehcache vs. GridDB vs. searchxml vs. SiteWhere

System Properties Comparison Ehcache vs. GridDB vs. searchxml vs. SiteWhere

Please select another system to include it in the comparison.

Editorial information provided by DB-Engines

Name

Description

A widely adopted Java cache with tiered storage options

Scalable in-memory time series database optimized for IoT and Big Data

DBMS for structured and unstructured content wrapped with an application server

M2M integration platform for persisting/querying time series data

Primary database model

Key-value store

Time Series DBMS

Native XML DBMS
Search engine

Time Series DBMS

Secondary database models

Key-value store
Relational DBMS

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

Score	4.79
Rank	#66	Overall
	#8	Key-value stores

Score	1.91
Rank	#123	Overall
	#10	Time Series DBMS

Score	0.00
Rank	#385	Overall
	#7	Native XML DBMS
	#24	Search engines

Score	0.07
Rank	#347	Overall
	#33	Time Series DBMS

Website

www.ehcache.org

griddb.net

www.searchxml.net/category/products

github.com/sitewhere/sitewhere

Technical documentation

www.ehcache.org/documentation

docs.griddb.net

www.searchxml.net/support/handouts

sitewhere1.sitewhere.io/index.html

Developer

Terracotta Inc, owned by Software AG

Toshiba Corporation

informationpartners gmbh

SiteWhere

Initial release

2009

2013

2015

2010

Current release

3.10.0, March 2022

5.1, August 2022

1.0

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

Open Source

AGPL version 3 and Apache License, version 2.0 , commercial license (standard and advanced editions) also available

commercial

Open Source

Common Public Attribution License Version 1.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++

Java

Server operating systems

All OS with a Java VM

Linux

Windows

Linux
OS X
Windows

Data scheme

schema-free

yes

schema-free

predefined scheme

Typing

predefined data types such as float or date

yes

numerical, string, blob, geometry, boolean, timestamp

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

SQL92, SQL-like TQL (Toshiba Query Language)

APIs and other access methods

JCache

JDBC
ODBC
Proprietary protocol
RESTful HTTP/JSON API

RESTful HTTP API
WebDAV
XQuery
XSLT

HTTP REST

Supported programming languages

Java

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

C++

most other programming languages supported via APIs

Server-side scripts

Stored procedures

yes

on the application server

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

Sharding

none

Sharding

based on HBase

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

Source-replica replication

yes

sychronisation to multiple collections

selectable replication factor

based on HBase

MapReduce

Offers an API for user-defined Map/Reduce methods

Connector for using GridDB as an input source and output destination for Hadoop MapReduce jobs

Consistency concepts

Methods to ensure consistency in a distributed system

Tunable Consistency (Strong, Eventual, Weak)

Immediate consistency within container, eventual consistency across containers

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 at container level

multiple readers, single writer

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

User concepts

Access control

Access rights for users can be defined per database

Domain, group and role-based access control at the document level and for application services

Users with fine-grained authorization concept

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

Jira Data Center user? Here's a critical Ehcache vulnerability to spoil your day
22 July 2021, The Register

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

How to partition Sonatype Nexus Repository: Targets, privileges, and roles
9 February 2010, Sonatype Blog

Implementing fallback with cached data
8 October 2018, O'Reilly Media

provided by Google News

TOSHIBA DIGITAL SOLUTIONS CORPORATION
1 November 2020, global.toshiba

Toshiba launches cloudy managed IoT database service running its own GridDB
8 April 2021, The Register

Now Features Scale-Out and Scale-Up combo for Petabyte-scale Data Management
3 December 2019, global.toshiba

Amazon Proposes to Develop New Data Center Campus in Virginia
26 August 2022, w.media

’s SQL Interface, Aims to Accelerate Open Innovation
17 June 2020, global.toshiba

provided by Google News

SiteWhere: An open platform for connected devices
11 July 2017, Open Source For You

Top Open-Source Tools for IoT Development in 2024
5 September 2024, Analytics Insight

11 Best Open source IoT Platforms To Develop Smart Projects
9 March 2023, H2S Media

provided by Google News

Share this page