In a uniform configuration, you can deploy multiple, identical True Caches that use the same True Cache database application service. Client sessions are evenly distributed among True Caches, which all cache the same set of data.
This diagram shows an example of a uniform configuration with the following elements:
- One primary database (
PRIMDBI) - Two True Caches (
TCDB1IandTCDB2I) - One remote listener (
sales_rl) - Two applications
When True Cache starts, the True Cache network name that is specified in the FAL_CLIENT parameter (TCDB1I or TCDB2I) is registered with the primary database network name that is specified in the FAL_SERVER parameter (PRIMDBI).
If the application handles connections manually, it sends queries to True Cache through a True Cache database application service, and it sends other queries and updates to the primary database through the primary database application service.
To achieve more application transparency, you can use the JDBC method and associate primary database application services with True Cache database application services. This diagram shows the following database application services:
- The primary database (
PRIMDBI) runs one database application service calledSALES. - Two True Caches (
TCDB1IandTCDB2I) share one database application service calledSALES_TC.
The two services are associated by setting the TRUE_CACHE_SERVICE parameter to SALES_TC for the primary database application service (SALES). The application's code only needs to know about the primary database application service (SALES). To use the SALES_TC database application service, the application changes the setReadOnly flag (TRUE or FALSE) of the SALES JDBC connection.
The True Caches and the primary database share a remote listener (sales_rl). If multiple True Caches exist and serve the same database application service, the listener automatically distributes and load balances sessions to each cache.