[EXTDAM-13] Have caching mechanism for connections to external dams Created: 22/Jul/19  Updated: 21/Feb/20  Resolved: 17/Feb/20

Status: Closed
Project: External DAMs
Component/s: None
Affects Version/s: None
Fix Version/s: 1.0

Type: Story Priority: Neutral
Reporter: Ilgun Ilgun Assignee: Jesus Alonso
Resolution: Done Votes: 0
Labels: None
Remaining Estimate: 0d
Time Spent: 4.5h
Original Estimate: Not Specified

Issue Links:
Relates
relates to BUILD-367 Add caffeine dependency Closed
Template:
Acceptance criteria:
Empty
Task DoD:
[ ]* Doc/release notes changes? Comment present?
[ ]* Downstream builds green?
[ ]* Solution information and context easily available?
[ ]* Tests
[ ]* FixVersion filled and not yet released
[ ]  Architecture Decision Record (ADR)
Epic Link: DAMs backend
Sprint: Add-Ons 30, Add-Ons 31
Story Points: 5

 Description   

As those operations are most likely expensive, we might cache some information in the memory. However, we cannot simply cache everything so we need to find a way to say what should be cached. Perhaps even connector themselves should know what should be cached.

  • Connector specific configurable caching mechanism
  • Connector would know and tell what to do
  • Non-cached objects still come from the connector together with cached objects

Generated at Mon Feb 12 01:51:02 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.