DBMS > Ehcache vs. Google BigQuery vs. Sphinx vs. Teradata

System Properties Comparison Ehcache vs. Google BigQuery vs. Sphinx vs. Teradata

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

Large scale data warehouse service with append-only tables

Open source search engine for searching in data from different sources, e.g. relational databases

A hybrid cloud data analytics software platform (Teradata Vantage)

Primary database model

Secondary database models

Document store
Graph DBMS
Spatial DBMS
Time Series DBMS

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

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

Score	60.38
Rank	#19	Overall
	#13	Relational DBMS

Score	5.98
Rank	#56	Overall
	#5	Search engines

Score	45.33
Rank	#21	Overall
	#15	Relational DBMS

Website

www.ehcache.org

cloud.google.com/bigquery

sphinxsearch.com

www.teradata.com

Technical documentation

www.ehcache.org/documentation

cloud.google.com/bigquery/docs

sphinxsearch.com/docs

docs.teradata.com

Developer

Terracotta Inc, owned by Software AG

Google

Sphinx Technologies Inc.

Teradata

Initial release

2009

2010

2001

1984

Current release

3.10.0, March 2022

3.5.1, February 2023

Teradata Vantage 1.0 MU2, January 2019

License

Commercial or Open Source

Open Source

Apache Version 2; commercial licenses available

commercial

Open Source

GPL version 2, commercial licence available

commercial

Cloud-based only

Only available as a cloud service

yes

DBaaS offerings (sponsored links)

Database as a Service

Providers of DBaaS offerings, please contact us to be listed.

Implementation language

Java

C++

Server operating systems

All OS with a Java VM

hosted

FreeBSD
Linux
NetBSD
OS X
Solaris
Windows

hosted
Linux

Data scheme

schema-free

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

full-text index on all search fields

yes

Join-index to prejoin tables, aggregate index, sparse index, hash index

SQL

Support of SQL

yes

SQL-like query language (SphinxQL)

yes

SQL 2016 + extensions

APIs and other access methods

JCache

RESTful HTTP/JSON API

Proprietary protocol

.NET Client API
HTTP REST
JDBC
JMS Adapter
ODBC
OLE DB

Supported programming languages

Java

.Net
Java
JavaScript
Objective-C
PHP
Python
Ruby

C++

unofficial client library
Java
Perl

unofficial client library
PHP
Python
Ruby

unofficial client library

C
C++
Cobol
Java (JDBC-ODBC)
Perl
PL/1
Python
R
Ruby

Server-side scripts

Stored procedures

user defined functions

in JavaScript

yes

UDFs, stored procedures, table functions in parallel

Triggers

yes

Cache Event Listeners

yes

Partitioning methods

Methods for storing different data on different nodes

Sharding

by using Terracotta Server

none

Sharding

Partitioning is done manually, search queries against distributed index is supported

Sharding

Hashing

Replication methods

Methods for redundantly storing data on multiple nodes

yes

by using Terracotta Server

none

Multi-source replication
Source-replica replication

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)

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

Since BigQuery is designed for querying data

ACID

Concurrency

Support for concurrent manipulation of data

yes

Durability

Support for making data persistent

yes

using a tiered cache-storage approach

yes

The original contents of fields are not stored in the Sphinx index.

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 privileges (owner, writer, reader) on dataset, table or view level

Google Cloud Identity & Access Management (IAM)

fine grained access rights according to SQL-standard

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.