System limits enforcement and alerting
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 661
- Forks
- 63
- PR merge metrics
- No merged PRs in 30d
Description
### Context
iWF is backed by Cadence/Temporal which has limits per workflow execution:
* Blob size limit: 2MB
* history event limit: 4MB
* Total history size limit: 50MB
Input/output size
## AC
Reject requests if
* Start workflow, signal/ workflow, or RPC internal channel message are exceeding 100KB
* Upsert data attribute is exceeding 100KB from activity
Emit an event for logging and metrics when
* Any request or message is reach 80% of the above rejection threshold
* Total history size is greater than 1MB (based on temporal sdk [value](https://github.com/temporalio/sdk-go/blob/41e9b33d85c067b75b3fea81e563cfe76fbd785d/internal/workflow.go#L1252))
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
The issue does not name files, tests, or entry points. Start by tracing workflow start, signal, RPC internal-channel, activity upsert, and history-size handling in the Go service and checking the Temporal limits referenced in the issue. Done means requests over 100KB are rejected, 80% thresholds and history over 1MB emit logging and metrics events, and tests cover these cases.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- backend-api-design, distributed-systems
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100