Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

As someone curious to try out Temporal. What makes you think it is not simple, is it tricky enough that one should avoid it?

What else makes this Trigger.dev stand out compared to Temporal? Temporal already has self hosting option, multiple language support and a battle proven history. Even if trigger looks good on paper, it would need some other really convincing reason for me to consider a completely fresh tool over something more proven, that appears to fill the same space.

Good to see some competition in this space though. Workflows are too important to be relegated to flaky scripts, diy workflow engines or worst of all: yaml-as-code.



I share that curiosity! Temporal looks great and is proven. Running it looks simple enough. I mean getting their self-hosted version deployed (to production). I was reading through their docs and that does _not_ look simple (to me). Plus the guide is open about being a work in progress (https://docs.temporal.io/cluster-deployment-guide#elasticsea...). I am going to try it at some point though.


The simplest way to self-host is with Render: https://render.com/docs/deploy-temporal

Scaling takes a lot of expertise, and I'd say almost everyone saves time & money and gains in reliability by using Temporal Cloud over self-hosting.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: