indeedeng / indeedeng/iwf

Future, maybe V2: use matching in server to invoke start/decide APIs instead of calling user code by rest APIs

Open
#47 1 comment 0 reactions 0 assignees View on GitHub
feature large
Dominant language
Go
Stars
661
Forks
63
PR merge metrics
No merged PRs in 30d

Description

1. In memory matching only. Activity task will wait for match and return , only wait for 1-2 sec to reserve the activity timeout for APIs
2. Test only
3. Disabled by default
4. IwfWorkflowType as queue name

Contributor guide

Open the contributing guide

Research direction

Start by tracing the activity task, in-memory matching, and the start/decide APIs described in the issue. Confirm how IwfWorkflowType is used as a queue name and how activity timeouts are handled. Done means the behavior is test-covered, disabled by default, and reserves only 1–2 seconds for matching.

Written by the indexing model from the issue text.

Assessment

Tech stack
go
Domain
api, backend, distributed-systems
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.