Child pages
  • Terracotta DB 10.2 Release Notes
Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Terracotta DB is a distributed in-memory data management solution for both operational and analytical workloads.  Terracotta DB has powerful query and computation capabilities, leveraging native JDK features such as Java Streams, collections, and functions. It supports the following sub-systems:

  • A storage sub-system fronted by TCStore API

  • A caching sub-system fronted by the next generation Ehcache API which includes and extends JSR 107

Both sub-systems are backed by the Terracotta Server, which provides a common platform for distributed in-memory data storage with scale-out, scale-up and high availability features.

Feature Highlights

  • AWS as a supported platform for Terracotta DB
  • Terracotta DB now supports docker-based container orchestration using Kubernetes
  • Advanced support for resilient failover through improved "Failover-tuning" option
  • Resiliency support for improved re-connection for both Ehcache and TCStore clients
  • Security enhancements including SSL support for Encryption and Authentication
  • SQL-like query capability using new Terracotta Textual Query Language 
  • Ad Hoc Query capability within Terracotta Management Console with new Terracotta DB Explorer
  • Numerous operational usability enhancements including Latency statistics and Query statistics monitoring

Summary of Changes


  • 2966 - Cluster tool "status" command shows inconsistent stripe contents

  • 2801 - "common name" in the server’s TLS/SSL certificate is not validated properly

  • 2450 - Two servers in a stripe can be mistakenly displayed as ACTIVE in TMC

  • 2993 - Improve impact of thread interrupt during reconnection

  • 2969 - ipwhitelist-reload returns success even if the command fails

  • 3022 - Reconnect attempts should use a distinct timeout

  • 3014 - fixed multiple cases where reconnect can fail


  • Terracotta BigMemory 4.x and Terracotta DB 10.x clients may be used simultaneously in the same application by ensuring ClassLoader isolation when initializing at least one of the clients.
  • No labels