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
Show HN: Durable Python Workflows
11–17 of 17 posts
Re: Show HN: Durable Python Workflows
#12I 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
Re: Show HN: Durable Python Workflows
#13> 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
#14Earlier quoted context omitted.
What is so hard about self-hosting Cadence or Temporal?
so last time i used temporal, it has 3-4 separate "services" that need to be deployed in a cluster configuration (not 1 instance) and then they are dependent on a performant cassandra cluster. its certainly not easy.
Re: Show HN: Durable Python Workflows
#15> 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
#16take 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
#17Earlier quoted context omitted.
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.
If someone is already using temporal cloud wouldn’t they be able to use oss AK and just point it at their cloud instance?