Exploring Temporal to stitch customer journey

I am exploring temporal to stitch my customers journey in an e-commerce platform. The workflow is supposed to start when a user clicks on ‘search’, and supposed to end when the customer finally places the order. Current objective of this workflow is to track user’s journey in the e-commerce funnel, and provide experience to the dropped off customers for resuming there transaction on the platform

Temporal seems like a really good fit with the offerings around resilience, very expressive state-machine support (Ex : scheduled transitions based on timers, etc), decoupling business logic vs orchestration, durable execution, etc.

Though looking very lucrative from the POC’s/reading i have done, looking for suggestions around if temporal has been battle tested at the scale of

  • 5000 new workflows (and growing) initiated every second (search scale)
  • Each workflow spanning max for 30 days
  • Each workflow has maximum 4 state transitions.

Any other thing which i need to be mindful of here.

Thanks