You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Adam Saghy (Jira)" <ji...@apache.org> on 2025/05/12 08:47:00 UTC
[jira] [Resolved] (FINERACT-2262) Improve cache handling in Fineract
[ https://issues.apache.org/jira/browse/FINERACT-2262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Adam Saghy resolved FINERACT-2262.
----------------------------------
Resolution: Fixed
> Improve cache handling in Fineract
> ----------------------------------
>
> Key: FINERACT-2262
> URL: https://issues.apache.org/jira/browse/FINERACT-2262
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Adam Saghy
> Priority: Major
> Fix For: 1.12.0
>
>
> Automatically register the caches with the default configuration.
> Adding option to customize the caches via configuration.
>
> *Explanation:*
> `CacheConfig` is used to register each caches that used in Fineract. It is using reflection to collect the usages and register the caches with default configuration (configurable via `application.properties`) or with custom configuration (if applicable, also via `application.properties`)
>
> *Example:*
> `application.properties`
> #Cache - Default
> fineract.cache.default-template.ttl=1m
> fineract.cache.default-template.maximum-entries=1000
>
> By default each caches expiration date is 1 minute and store maximum 1000 entries in heap memory.
>
> *Option for* *customisation*
> #Cache - Customization
> fineract.cache.custom-templates.userTFAccessToken.ttl=2h
> fineract.cache.custom-templates.userTFAccessToken.maximum-entries=10000
>
> Via the `custom-templates` we can define custom configuration for caches based on the cache identifier.
>
> In the above example, we are using different cache configuration for `userTFAccessToken` cache.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)