News for hackers. Stuff that matters.
Re:Just Use Postgres for Durable Workflows by temporal_thr321 on Thursday May 28, 2026 @06:34PM (#48316482)
I was not clear; I did not mean not 200 a day, it's 10s of thousands of concurrently running workflows, sometimes into the hundreds of thousands, each with 200 events. We run many hundreds of thousands of these a day.

Temporal was a bad fit for us, and we regret it deeply.

Re:Just Use Postgres for Durable Workflows by mikert89 on Thursday May 28, 2026 @10:58PM (#48318463)
what would you use instead?
Re:Just Use Postgres for Durable Workflows by quacker on Friday May 29, 2026 @01:49AM (#48319532)
Ah. So multiple billion actions per month, and probably multiple million dollars per year on their cloud, if they can even support that load (plus, the vendor lock in and etc). Makes sense.
Re:Just Use Postgres for Durable Workflows by gaurdro on Wednesday June 10, 2026 @10:42AM (#48477040)
I'm reasonably sure their cloud product can handle that. you might be in the scale where they want to hold your hand in the transition though.

Given the open source nature of the product, I'm not sure what vendor lock-in you mean. Migrating off cloud to your own infra again is doable. https://daylight.ai/blog/how-we-migrated-off-temporal-cloud-...

Re:Just Use Postgres for Durable Workflows by tomwheeler on Wednesday June 10, 2026 @02:40PM (#48480792)
Hi, Temporal employee here. Just want to confirm that Temporal Cloud can and does handle this scale, well beyond it, in fact.

As our CEO and co-founder Samar Abbas stated in the keynote at this year's Replay conference (https://youtu.be/BxEB7Y2U9oU?t=532), Temporal Cloud is currently handling 35 billion workflows per day. If you assume that each Workflow averages 10 actions, that translates to more than 10 trillion actions per month.

Later in that keynote, a VP from OpenAI talks about the scale at which they are using Temporal Cloud. That'll give you a sense of the volume for a single customer (obviously a very large one).