Does this let you take business SOPs and convert it into workflows?
You get much better e2e observability + debugging this way. Also can more easily model higher-level processes and handle concurrently-running versions of workflows.
Side note: we also have durable execution within a Task Worker via `context.executeAndCheckpoint(...)`
coltmcnealy•1h ago
Business-as-Code lets you write code that orchestrates your business process at a high level, while handling low-level integration for you. Similar idea to Infrastructure-as-Code but for your business process logic rather than infra configuration.
LH also has a two-way integrations with Kafka: our Kafka Connectors signal waiting workflows or trigger new ones, and the Output Topic produces a CDC-style stream of workflow events into Kafka.
Would love feedback if you're dealing with stuff like retries / DLQ's / SAGA / Outbox Pattern, etc.
gwen-shapira•1h ago
You may be under-selling LittleHorse a bit (here and even in the README). Few things I find cool about it:
- How easy it makes writing human-in-loop workflows (or these days, agent-in-loop). Everyone wants human-in-loop, but very few workflow frameworks make it simple.
- Using LittleHorse to introduce stateful guardrails to agentic flows. This helps with context compaction and other safety issues.
- The new (experimental?) generation of workflows from JSON. This simplifies things quite a bit.
coltmcnealy•1h ago
jcustenborder•48m ago