Fee estimate server side cache

[just-a-node]

Description

Minimal changes to enable optional caching on the estimateRelayerFee route. This can be extended to other routes if necessary. Opted not to intercept axiosGet requests in the Gelato calls as this requires changes in the utils package and would make removing the server dependency more complex later. This should suffice for reducing latency since most client calls will not use the optional params in SdkEstimateRelayerFeeParams and will hit the cache for subsequent requests to the same originDomain/destinationDomain.

Type of change

• Docs change / dependency upgrade
• Configuration / tooling changes
• Refactoring
• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Requires changes in customer code

High-level change(s) description - from the user's perspective

Related Issue(s)

Fixes #4223

Related pull request(s)

[sanchaymittal]

i think we should do that cache at the sdk code only, instead of adding it to server. Server should be purely a wrapper around the sdk.
@just-a-node

[sanchaymittal]

best to keep cache at core-sdk, and keeping server wrapper to main functions

[just-a-node]

@sanchaymittal Wait, sdk-server is what's being hosted. We're going to have a separate wrapper package that mimics the client SDK interface and calls these server routes. So this cache is at the API side

[sanchaymittal]

From what I can recall from the last discussion, Is that we want to release under package @connext/sdk only with different versioning. So ideally we want to have cache being optional at core-sdk itself and wrapper at Server. And sdk turned into wrapper of api calls of server.

[just-a-node]

I think we have a similar understanding, but see structure in #4228.

What I was assuming is:

• core SDK stays the same
• sdk server stays basically the same, now it's hosted
• new package wraps api calls to the server and it's published to @connext/sdk

[just-a-node]

The cache implemented here is the middleware described in #4223. This is caching at the API layer, not the service level of core sdk

[rhlsthrm]

Nice! I guess we'd need ops setup for this.

[just-a-node]

Yes for redis and the right configs to feed server