Centralize handling of caches [DBZ-1490]
- Dominant language
- HTML
- Stars
- 6
- Forks
- 8
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 1
Description
Migrated from [DBZ-1490](https://issues.redhat.com/browse/DBZ-1490)
Debezium already contains multiple places where caches (usually {{BoundedConcurrentHashMap}}) are used. Every place hardoceds its parameters and there is no coordination between them.
We should introduce a central component that will
* provide cache instances based on logical names
* allow those caches instances to be configurable via connector properties like {{cache.field-name-sanitizer.size}} etc.
* will expose the caches metrics via JMX
It doesn't need to be exposed in general documentation but can be really useful for perf tuning guide.
Contributor guide
Research direction
No files, tests, or entry points are identified in the issue. Start by locating the existing BoundedConcurrentHashMap cache uses and connector-property handling, then determine how a central component could provide logical-name caches, configurable sizes, and JMX metrics; done means all relevant caches use it and the requested configuration and metrics are available.
Written by the indexing model from the issue text.
Assessment
- Domain
- backend, observability, performance
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100