Business-as-Code with LittleHorse 1.0
github.com
Business-as-Code with LittleHorse 1.0
1–9 of 9 posts
Re: Business-as-Code with LittleHorse 1.0
#2Business-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.
Re: Business-as-Code with LittleHorse 1.0
#3Does this let you take business SOPs and convert it into workflows?
Re: Business-as-Code with LittleHorse 1.0
#4We just launched LittleHorse Server 1.0: an open-source workflow engine for Business-as-Code (SDKs in Java, Python, C#, and GoLang), built for microservices, event-driven systems, and long-running processses. 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 lo…
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.
Re: Business-as-Code with LittleHorse 1.0
#5This is interesting. How does it compare with Temporal or other orchestrators? 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(...)`
Re: Business-as-Code with LittleHorse 1.0
#6We just launched LittleHorse Server 1.0: an open-source workflow engine for Business-as-Code (SDKs in Java, Python, C#, and GoLang), built for microservices, event-driven systems, and long-running processses. 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 lo…
Congrats on the launch! 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 iss…
Re: Business-as-Code with LittleHorse 1.0
#7Re: Business-as-Code with LittleHorse 1.0
#8We just launched LittleHorse Server 1.0: an open-source workflow engine for Business-as-Code (SDKs in Java, Python, C#, and GoLang), built for microservices, event-driven systems, and long-running processses. 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 lo…
Congrats on the launch! 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 iss…