Hey everyone ![]()
I’ve been playing with an idea: what if building long-lived, stateful things on Temporal in Go felt more like writing actors — but without codegen, reflection, or hiding Temporal under the rug?
So I built a small SDK called Tactors:
GitHub - tactors/sdk: Typed, builder-first actor SDK for Go built on Temporal.io: describe stateful workflows, commands, queries, and activities with fluent APIs, then run them deterministically across Temporal workers and testsuite scenarios.
What it does:
You define an actor with a clean builder: state type + commands + queries + optional activities.
The SDK wires it to Temporal for you (workflow + activities + continue-as-new, snapshots).
Everything is strongly typed — no interface{}, no manual payload decoding.
Comes with a simple testkit on top of the Temporal testsuite.
And you still “feel” Temporal — queues, workers, task routing, activity options, etc.
So it aims to be a middle ground: keep Temporal’s power, reduce boilerplate, add an actor mental model.
If you have 5–10 minutes to skim the repo or try a tiny actor, your thoughts will help shape the next iteration.Thanks a lot — and happy to answer any questions! ![]()