A recreation booking path crosses API Gateway → Function → Queue → OKE worker. How should end-to-end journeys be sized in the suite?
Select an answer to reveal the explanation.
Short Explanation
A parade across four city systems is expensive and brittle. Keep a few to prove the wires connect; catch most bugs at the desk that changed with unit and contract tests.
Full Explanation
End-to-end paths that cross API Gateway, Functions, Queue, and OKE are valuable but costly and brittle. Professional suite shape keeps a thin slice of such journeys for wiring confidence and puts the bulk of regression coverage in unit and contract tests for the changed service. Replacing those layers with one giant multi-service scenario slows feedback and couples teams.