This is working so well ! Thanks Christoph and team.
Question: I thought Fusio did this but just can't find this in the documentation - using HttpProcesor, are we able to cache the results of larger queries for faster responses?
1) Consumer X makes are request to Route Y ... this takes 20 seconds to process.
2) Consumer Z makes a request to Route Y in 30 seconds ... is there a way of caching the results for route Y from step 1 ?
3) Ideally be able to set a setting to say Route Y can only be run, say, every 5 minutes and if it gets called more frequently, then send back the results we already have.
Use case would be:
"As an administrator I'd like to be able limit expensive HTTP -forwarded hits on the upstream server, but still provide results to the consumers by setting a time threshold during which if the same expensive route is requested, then we send back the results we have on hand. If we don't have a result for the route during the threshold period, then Fusio can submit the query to the upstream server."
Is there a feature like this that we can utilize today? My apologies if it is in the docs - just can't seem to find it.