Page Comparison

...

The following diagram displays the main components and actors involved in the flow.

...

1. Routes Cache with Expiration Policy:

   • Purpose: The mgr-URLs module maintains a cache of routes that includes information about various system/timer interfaces and their respective routes. This cache has an expiration policy to ensure that the information remains up-to-date and valid.

   • Functionality: When a request for a specific route (e.g., /timer-urlA) is received, the module checks its cache for the corresponding route. If the route information is available and valid, it proceeds to use it. If the information is expired or not found, the module queries relevant systems to fetch and update the route information.

2. Route Resolution:

   • Resolving Routes: The module resolves the actual route for the requested URL, ensuring that the correct path is used for system/timer calls. This involves determining the correct endpoint based on the module version and the specific tenant making the request (e.g., tenant Diku).

   • Integration with Other Modules: It interacts with mgr-Tenant-Entitlements and mgr-Applications to resolve the module version and obtain the correct route information. This ensures that the requests are directed to the appropriate module version and interface.

3. Lightweight and Simple: mgr-URLs module does not use any persistent storage and integrates only with mgr-Tenant-Entitlements and mgr-Applications