←back to thread

Show HN: Durable Python Workflows

(github.com)
64 points itayd | 3 comments | 22 Apr 25 22:41 UTC | HN request time: 0.863s | source
Show context
pm90 ◴[22 Apr 25 23:18 UTC] No.43767190[source]▶
> 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.

replies(4): >>43767240 #>>43767246 #>>43767329 #>>43768928 #
1. ofrzeta ◴[23 Apr 25 05:34 UTC] No.43768928[source]▶
What is so hard about self-hosting Cadence or Temporal?
replies(1): >>43771036 #
2. rrdotspace ◴[23 Apr 25 11:52 UTC] No.43771036[source]▶
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.
replies(1): >>43771441 #
3. ofrzeta ◴[23 Apr 25 12:44 UTC] No.43771441[source]▶
I didn't want to question it, because I have no experience with it. So thanks for the info.