Comment by pm90
1 day ago
> 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.
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?
yup!
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.
I didn't want to question it, because I have no experience with it. So thanks for the info.