temporalio / temporalio/temporal
Ability to define execution order of async activity invocations
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Go
- Stars
- 23.2k
- Forks
- 1.9k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 228
Description
Currently Temporal does not guarantee relative ordering of async started activities.
User here requested that for his use case Temporal would provide such guarantee for his scenario.
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
Start with the issue description and the linked Temporal community discussion to understand the requested ordering guarantee and its intended scenario. The issue names no files, tests, or entry points, so identify the relevant async activity invocation and scheduling paths before defining how relative ordering would be specified and verified.
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
- 20/100