Synchronous microservice orchestration

Forgive the basic question, but I’m looking to understand the practicalities and any best practices for using Temporal as a real-time synchronous orchestration platform for microservices.

What I mean here is basically putting Temporal between an API Gateway and other microservices to handle any requests/responses that require actions across multiple services - for example, adding an item to an order might require a stock check/reservation at the inventory service - and then passing a response back to the client (eg successfully got the item, failed to reserve inventory, etc).

Does this really work at scale? Do workflows (at scale) execute and return responses quick enough? Do we start hitting concurrent workflow execution limits at some point?

Given the examples like the e-commerce sample it seems like this does work, but any docs or best practices on operating like this at scale would be awesome.

Yes, it works at scale. But this makes sense only if you need to guarantee execution of the sequence of steps in the presence of failures. In the synchronous case the most common use case is SAGA pattern, when an error is returned to the user immediately and then compensations happen in background.