Hacker News: temporal_thr123

New comment by temporal_thr123 in "Building durable workflows on Postgres"

temporal_thr123 — Thu, 28 May 2026 19:34:10 +0000

Since I'm in a ranting mode -- here's a good example: you're limited to _ONE_ IO per shard in the history service:

https://github.com/temporalio/temporal/blob/e22e6304b3c4a409...

Temporal does a crazy amount of database operations and all of these are behind that mutex.

Oh, and you can't change the shard count on existing clusters.

Great stuff.

New comment by temporal_thr123 in "Building durable workflows on Postgres"

temporal_thr123 — Thu, 28 May 2026 19:24:52 +0000

Sure, if you wanna run a 48 node cassandra cluster...

New comment by temporal_thr123 in "Building durable workflows on Postgres"

temporal_thr123 — Thu, 28 May 2026 19:21:21 +0000

I run a large on-prem temporal setup - throwaway acct as they will likely out me.

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

If you're doing anything non-trivial (say, 200+ events/workflow) and you need to run only a couple hundred of them concurrently all day, you're going to spend millions on infra, and it's still going to absolutely suck.

Try running their own benchmarks, the numbers are pathetic.

Their sales team is also absolutely appalling and desperate.

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

Don't get trapped into nexus, and if the sales team call you make sure legal is in the room.