Details
-
Story
-
Resolution: Unresolved
-
Neutral
-
None
-
None
-
None
-
-
Empty show more show less
-
Yes
-
Yes
-
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.)
Checklists
Acceptance criteria
Attachments
Issue Links
- mentioned in
-
Page Loading...