[MGNLCT-109] Cache external content Created: 13/Feb/19  Updated: 02/Apr/19

Status: Open
Project: Content Types
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Story Priority: Neutral
Reporter: Christopher Zimmermann Assignee: Unassigned
Resolution: Unresolved Votes: 1
Labels: None
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

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)
Release notes required:
Yes
Documentation update required:
Yes
Epic Link: External Content
Sprint: Phase 4

 Description   

As a developer, I want my content to be performant and highly available even when using external content.

For example:

  • I have a personalization trait that uses REST to get information from a CRM. It would be inefficient if the REST call has to be performed with evey single page request, I would like the response to be cached - for example for 1 minute or 10 minutes - or based on other critiera.

Acceptance Criteria:

  • I can configure a caching strategy for the external content.
  • I can configure a command endpoint on magnolia to invalidate the local cache of external content.
  • If the external system is offline, cached content will still be displayed.
  • Works with light development.

(Additional benefits to caching: Caching remote content can reduce costs in case there is a charge or limit on the endpoint for the external content. It can keep the external content available if the external system is unavailable.)


Generated at Mon Feb 12 00:37:14 CET 2024 using Jira 9.4.2#940002-sha1:46d1a51de284217efdcb32434eab47a99af2938b.