Benefits of TAFJ Caching

This section emphasizes on how TAFJ Caching improves the execution time of Temenos Transact.

• TAFJ Caching caches a set of defined (mostly) read-only tables, which are defined in the TAFJ_CACHE table.
• When a record is read from the database, the record is cached as a dynamic array (regardless of the cache provider). Subsequent reads go to the cache first to check if the record is there. When the record is present, it is called a cache hit and if not it is called a cache miss.
• The record is removed from the cache before any write occurs so that any subsequent read will get fresh data from the database. Thus, it is better to configure tables that are written infrequently to avoid cache misses.

  

• The TAFJ Monitor helps you to track the cache read time.
• The TAFJCaching.jar file supports Apache Ignite 2.0 and later, Oracle Coherence, JBoss Data Grid, and WebSphere eXtreme Scale.