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
Order module (or microservice) queries a customer from the customer module (or microservice) and caches the result in the distributed cache. Then the customer module invalidates (simply removes) the cache item when the original customer changes.
The following figure shows it in a monolith modular application:
We typically write such a code in the order module:
This can be automated if we somehow enable client-side caching to dynamic/static client proxies and also application services with a simple attributed.
This is another typical code to invalidate the cached item:
We may also automate this with a simple configuration.
The text was updated successfully, but these errors were encountered:
Consider the following scenario:
Order module (or microservice) queries a customer from the customer module (or microservice) and caches the result in the distributed cache. Then the customer module invalidates (simply removes) the cache item when the original customer changes.
The following figure shows it in a monolith modular application:
We typically write such a code in the order module:
This can be automated if we somehow enable client-side caching to dynamic/static client proxies and also application services with a simple attributed.
This is another typical code to invalidate the cached item:
We may also automate this with a simple configuration.
The text was updated successfully, but these errors were encountered: