agent-substrate / agent-substrate/substrate
Enable caching for the Router for ResumeActor
Open
area/api
kind/feature
- Dominant language
- Go
- Stars
- 1.8k
- Forks
- 316
- Avg merge
- 2d 43m
- Merged PRs (30d)
- 287
Description
We should understand how to cache the metadata about the Actor after a successful resume. Currently every request ends up hitting the ATE API server for the current Actor. Being able to cache the state and response will be able to cut down significantly on the API.
Contributor guide
Assessment
This issue has not been assessed yet.