You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The ZDS actions geefZaakDetails and geefLijstZaakdocumenten are good examples of actions that are often called for the same object. Often these are called when users are navigating in the ZDS application. Also objects in the Catalog API practically never change, so caching these would save a lot of traffic too.
The Frank!Framework already supports multiple caching solutions. It should be just a matter of configuring one and enabling it.
Add and configure caching solution in development docker-compose
Add and configure caching solution in helm chart
The text was updated successfully, but these errors were encountered:
The ZDS actions geefZaakDetails and geefLijstZaakdocumenten are good examples of actions that are often called for the same object. Often these are called when users are navigating in the ZDS application. Also objects in the Catalog API practically never change, so caching these would save a lot of traffic too.
The Frank!Framework already supports multiple caching solutions. It should be just a matter of configuring one and enabling it.
The text was updated successfully, but these errors were encountered: