Caffeine configuration - Allow global default configuration

[renzodf]

Description

Hello,

Currently, "By default, caches do not perform any type of eviction if not configured." and the configuration is done trough a set of configuration variables (quarkus.cache.caffeine."cache-name".*). This requires a configuration per cache, which can be extensive if the number of cache is high.

It would be nice to introduce default configuration keys to allow the configuration of all caches in few lines:

quarkus.cache.caffeine.initial-capacity
quarkus.cache.caffeine.maximum-size
quarkus.cache.caffeine.expire-after-write
quarkus.cache.caffeine.expire-after-access
quarkus.cache.caffeine.metrics-enabled

Note: initial-capacity and maximum-size would configure each cache individually -> will not act as global limits.

Cheers,
Renzo

Implementation ideas

No response

[quarkus-bot]

/cc @gwenneg

[geoand]

@gwenneg this sounds reasonable to me. WDYT?

[gwenneg]

I like this global default config idea. It is totally reasonable and a great enhancement.

Note: initial-capacity and maximum-size would configure each cache individually -> will not act as global limits.

@renzodf I'm not sure I understood what you meant here. Would initial-capacity and maximum-size be treated differently than other config keys? A global config value (which would act as a global limit) would make sense to me.

[renzodf]

@gwenneg Thanks for the dev :)

[gwenneg]

You're welcome!

[fabrii]

Hi @geoand and @gwenneg! This seems to not be working in Quarkus 2.16.7.

Log:

Unrecognized configuration key "quarkus.cache.caffeine.expire-after-write" was provided; it will be ignored; verify that the dependency extension for this configuration is set or that you did not make a typo

[geoand]

It was added in Quarkus 3

[fabrii]

Oh, is there any chance to backport it? :)

[geoand]

Probably not since we don't plan to maintain 2.16 indefinitely