|
|
|
|
|
|
by temporal_thr321
27 days ago
|
|
|
Not a couple hundred in one day, a couple hundred being started, concurrently, every second in a day. Each with ~200 events. We need a 12 node cassandra cluster for this, with 64cpu nodes. So no, it's not a couple of services and a postgres. Sales team, as we are an enterprise, and they want to extract money from us. |
|
|
If you have 200 WF’s/sec each with 200 events, it sounds to me that you have a sizeable amount of work flowing through this system. 17 million workflows per day? Can I call these transactions?
Do these transactions add value to your business? Do you need durable execution for all these workloads?
Temporal is just a tool; and like any tool it can be misused. For the classic “book a hotel + airline, handle the partial failures” case, 17 million bookings a day would imply you should be thrilled with Temporal.
If you are using it to perform WAF in a firewall; you would be less thrilled. The scale you are describing, and that you aren’t super excited about the incredible amount of money pouring in, makes me question if the use-cases are fitting the tool.