temporalio / temporalio/temporal
Support activity caching through sticky routing by user provided key
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Is your feature request related to a problem? Please describe.
Users want to cache activity results to improve performance. Currently there is no built-in way to provide activity routing to the same host by user provided id. For example Kafka consumers get this out of the box.
Describe the solution you'd like
Support worker options to enable this feature. Support activity invocation option to specify a routing key.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files, tests, or entry points are named. Start by locating worker options and activity invocation APIs, then read the existing sticky-routing behavior and related tests. Done should include a defined user-provided routing-key flow for activity calls and coverage for the worker and invocation options.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- distributed-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100