Show HN: Durable Python Workflows

#1

Post by itayd » Tue, Apr 22, 2025, 10:41 PM UTC

Show HN: Durable Python Workflows
github.com

Re: Show HN: Durable Python Workflows

#2

Post by pm90 » Tue, Apr 22, 2025, 11:18 PM UTC

> In addition, it is a durable execution platform for long-running and reliable workflows. It is based on Temporal, hiding many of its infrastructure and coding complexities.

You only hide it for as long as things go smoothly. When a thing breaks then ur hosed. Having seen people try to self host cadence/temporal (not super easy) this makes me skeptical.

Re: Show HN: Durable Python Workflows

#3

Post by itayd » Tue, Apr 22, 2025, 11:27 PM UTC

pm90 wrote: post #2

> In addition, it is a durable execution platform for long-running and reliable workflows. It is based on Temporal, hiding many of its infrastructure and coding complexities. You only hide it for as long as things go smoothly. When a thing breaks then ur hosed. Having seen people try to self host cadence/temporal (not super easy) this makes me skeptical.

In previous life I've been self hosting Cadence and it worked quite well. We then moved to Temporal cloud which was even easier.

That said, if you use autokitteh.cloud, you don't need to worry about Temporal as we're doing all that management behind the scenes.

Re: Show HN: Durable Python Workflows

#4

Post by akdor1154 » Tue, Apr 22, 2025, 11:27 PM UTC

pm90 wrote: post #2

> In addition, it is a durable execution platform for long-running and reliable workflows. It is based on Temporal, hiding many of its infrastructure and coding complexities. You only hide it for as long as things go smoothly. When a thing breaks then ur hosed. Having seen people try to self host cadence/temporal (not super easy) this makes me skeptical.

My thoughts as well.. Libraries where the only reason to exist is 'hide this other complex library in the cupboard so you don't have to learn it' almost never achieve that goal, and are generally harmful to net complexity imho.

Re: Show HN: Durable Python Workflows

#5

Post by itayd » Tue, Apr 22, 2025, 11:31 PM UTC

akdor1154 wrote: post #4

pm90 wrote: post #2

> In addition, it is a durable execution platform for long-running and reliable workflows. It is based on Temporal, hiding many of its infrastructure and coding complexities. You only hide it for as long as things go smoothly. When a thing breaks then ur hosed. Having seen people try to self host cadence/temporal (not super easy) this makes me skeptical.

My thoughts as well.. Libraries where the only reason to exist is 'hide this other complex library in the cupboard so you don't have to learn it' almost never achieve that goal, and are generally harmful to net complexity imho.

Hiding is actually not the main thing here. AK allows you to "deploy in a click" instead of deploying the actual workers. We also provide integrations with built in authentication for external services such as Slack, JIRA, etc.

Re: Show HN: Durable Python Workflows

#6

Post by [deleted] » Tue, Apr 22, 2025, 11:40 PM UTC

pm90 wrote: post #2

> In addition, it is a durable execution platform for long-running and reliable workflows. It is based on Temporal, hiding many of its infrastructure and coding complexities. You only hide it for as long as things go smoothly. When a thing breaks then ur hosed. Having seen people try to self host cadence/temporal (not super easy) this makes me skeptical.

[deleted]

Re: Show HN: Durable Python Workflows

#7

Post by itayd » Wed, Apr 23, 2025, 1:55 AM UTC

Hey, author here. We love durable functions and the ease it provides for building stuff. We provide an OSS as well as SaaS "serverless" platform to easily get started with durable functions using vanilla python.

Please take a look as well at https://github.com/autokitteh/kittehub which is full of examples. Also you can use https://autokitteh.cloud for free with some limits.

Re: Show HN: Durable Python Workflows

#8

Post by ofrzeta » Wed, Apr 23, 2025, 5:34 AM UTC

pm90 wrote: post #2

> In addition, it is a durable execution platform for long-running and reliable workflows. It is based on Temporal, hiding many of its infrastructure and coding complexities. You only hide it for as long as things go smoothly. When a thing breaks then ur hosed. Having seen people try to self host cadence/temporal (not super easy) this makes me skeptical.

What is so hard about self-hosting Cadence or Temporal?

Re: Show HN: Durable Python Workflows

#9

Post by opiniateddev » Wed, Apr 23, 2025, 5:45 AM UTC

take a look at https://github.com/conductor-sdk/conductor-python which is easier and will not force you to write with specific framework.

Re: Show HN: Durable Python Workflows

#10

Post by vivzkestrel » Wed, Apr 23, 2025, 6:24 AM UTC

I am sorry i dont understand, what exactly does this library do? Is it a competitor to rapidAPI that lets you quickly integrate APIs in your python app