Terracotta Ehcache is an innovation release which is an improved version of Java’s de facto caching API, Ehcache. It has a powerful, streamlined, modernized caching API taking advantage of newer Java features as well as the capability to be used via the JSR-107 “JCache” API.
Revamped API that leverages Java generics and simplifies Cache interactions
Full compatibility with javax.cache API (JSR-107)
Offheap storage capabilities, including offheap only caches
Out of the box Spring Caching and Hibernate integration thanks to the javax.cache support
- Support Custom Serializers
- In-memory storage with optional persistence to disk and ultra-fast recovery
- Java-based Key/Value store optimized for caching workloads
- The industry’s first and best Offheap storage capabilities
Supports various scale-out and HA deployment configurations
Flexible, fine-granular configuration of availability and consistency
- Simplified Terracotta Server Platform
- The new Terracotta Server offers a much simplified and pluggable platform
- Reduced inter-stripe communication resulting in less network overhead
- Better componentization
- Support for multiple In-Memory storage engines & Clustered entity types
- Improved Life-cycle management of Server entities.
- Improved baseline for future platform enhances to support enhanced feature like dynamic scaling, sophisticated data locality, partial availability etc.
- New Improved Monitoring Architecture
All Management Console requests are served by the Management Server without any impact on the clients connected to the server
- TMC performance is not impacted by the number of clients connected to the server.
- TC Server and clients can now server, extremely large number of TMC request with any performance impact on the operations.
Clients only talk to the Terracotta Server and pushes data on defined interval.
- Less noisy and more accurate
- Significant performance improvements
Summary of Changes in 10.0.0.2
1828 – Aligned handling of relative file path to data-root-config and servers/server/log
1829 – Servers drop-down list in monitoring view now displays stripe ID in addition to server name
1831 – Added a default for attribute, is the default when using builders
Renamed to and made to be optional just like in the builders
1832 – Resolved issue where the Hybrid sizeInBytes() does not take into account the actual data size which makes FRS SizeBasedCompactionPolicy become hyper aggressive in compacting data on systems that has only hybrid cache tiers.
1869 – Namespace of data-roots and frs-platform-persistence elements has been changed in tc-config as follows. If you have any existing tc-config, you need to update it to reflect new namespace in order to make it work with 10.0.0.2.