temporalio / temporalio/sdk-php
Simplify developer experience by replacing yields with Fiber suspension
Nobody has claimed this yet.
- Dominant language
- PHP
- Stars
- 421
- Forks
- 64
- Avg merge
- 1d 1h
- Merged PRs (30d)
- 11
Description
Personally I think reading Temporal workflows in PHP are very confusing due to the way you have to yield activities and timers.
Next to that I don't like the fact that I need to use RoadRunner and async PHP only to execute some workflows.
Recently I implemented an SDK in PHP for Absurd durable workflow engine using Fibers.
Basically when a workflow wants to suspend execution it triggers Fiber::suspend with the relevant info.
The SDK then reads the value and can decide to resume the Fiber if needed.
Just wanted to share this as I think it's an interesting alternative or a way to simplify the Temporal SDK.
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 reviewing the current yield-based workflow behavior and the linked Absurd PHP SDK's Fiber approach, then define agreed suspension and resumption requirements and tests before implementation.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- php
- Domain
- backend
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100