The benefit is (only ?) easy of scaling, IMHO. How solve this? I understand that GO keep the ordering of the calls and is not harder than doing imperative...
In terms of debugging issues when in live, you have to rely on tracing and let something such as Logstash handle search, etc.
The ordering of the workflow is preserved. As I explained, FraudCheck is only ever done after an order's payment has been authorised.
Hope this makes sense.
No. No, this is terrifyingly incorrect. Making each component do the right thing in isolation is easy. Most of the difficulty in systems - in developing, testing, and debugging them - arises from what the components do when they're together, because it turns out your ideas about how they need to behave in isolation were mistaken.
Or stop when a certain value arrive, and inspect the code. If this could be done with actor/csp, then is good idea to jump onto it.