Temporal

“I have big respect for what Maxim and the team built, and both systems are essentially open and free”

“It does work well to implement a multi-system transactional workflow broken down into retryable steps”

“a pretty large amount of overhead, both in performance and (I think more importantly) cognitive”

“The ability to see what's happening when and where across a single workflow run is a dream compared to all the traditional logging approaches I've seen.”

“It absolutely still has some considerable pain points though, and I find it difficult to use for larger tasks”

“You buy into more complexity upfront, but it makes the application code way simpler and easier to manage overall.”

“solid failure-resistant infra. Companies could set the same thing up with an in-house team, but it's pretty great to be able to click a button”

“the best substrate for these kind of agents are durable workflow engines. I'm currently supporting Temporal.”

“software rarely just works and impresses me and Temporal for my local machine orchestrating genuinely did”

“They ship Helm charts so reality is somewhere between "helm deploy" and "substantial ops burden".”

“I see this as Temporal surfacing inherent complexity of the domain in a way that forces the developer to consider it”

“Temporal is amazing, it feels much better than previous orchestrators I used like Prefect or Airflow.”

“Temporal feels massive, I tried it for a small workflow embedded on my system, and worked fine”

“paying more money than you expected for temporal's managed solution or taking on substantial ops burden”

“It makes the process of dealing with API retries and organizing workflows and tasks really simple.”

“I find it very powerful and easy to work with and has really helped move lifecycle logic out of APIs”

“It sucks to run yourself. Docs on running/errors are non-existent. Their helm charts are broken.”

“I thought Temporal was overly complex, but as you said the best part is it does enforce good engineering practices.”

“I tried their Cloud offering and was appalled at their pricing. I burned through the $1,000 free credits before I even got something to production.”

“From a Developer standpoint, the SDK is quite nice though.”

“Temporal is, in my opinion having run it in prod for over a year - poorly designed, slow and ridicliously heavy infra wise.”

“Temporal is a better design and one that's less likely to lead non-experts to make serious mistakes.”

“making time handling explicit and predictable, which is probably what developers needed all along”

“The whole point of the library is to be explicitly about what kind of date/time data you're working with”

“a lot of the biggest gains in Temporal are the "Plain" family for "wall clock times"/"wall calendar dates"”

“PlainDate and ZonedDateTime finally give us types that match how humans actually think about time”

“All Temporal objects are easily (de)serializable, though. `.toString` and `Temporal.from` work great.”

“Temporal fixes both by forcing you to be explicit about timezones through ZonedDateTime vs PlainDate”

“It actually can replace the semaphores, checkpointing, cancellation and even add crash recovery”

“every workflow instance can have a shit ton of long running state that gets persisted and rehydrated at will”

“Even in a product as technically wonderful as Temporal, we can have relatively simple oversights like this that lead to cross tenant leakage.”

“It's only been a few months since I started deploying Temporal at work, and there's no way that I would try implementing all this in-house.”

“the only boilerplate is like 3 lines of code for a simple workflow function to call the activity”

“At my current job we are forced to use Temporal for all background processing, which for small tasks is just a lot of boilerplate.”

“I am using Temporal, Durable execution state was a big problem for orchestrating a single backend”

“for mature production system see temporal. their magic sauce is good intermediate states.”

“Durable‑execution frameworks (DBOS/Temporal/etc.) give you retries, state, and consistency out of the box.”

“Temporal is an AMAZING piece of software, however I don't believe it's a replacement for something more simple like Celery.”

“Temporal does make it easy to mint an idempotency key by concatenating workflow run id and activity id”

“durable workflow platforms such as temporal.io which also bring the ability to spread the load over many workers”