Short answer: A managed mock cloud is a hosted service for stubs; the Hub hosts the mock and the docs together from the spec. The first is a hosted mock; the second is a hosted contract, so the mock and the reference cannot be out of sync.
What a mock cloud provides
Hosted stubs, collaboration, and a free call allowance. It is the right tool when the mock is a standalone hosted service.
What the Hub provides
| Property | Mock cloud | Hub |
|---|---|---|
| Hosted surface | Mock | Mock + docs |
| Source | Stub code | Spec |
| Sync | Manual | On publish |
| Agent tools | Separate | From spec |
Why the shared host matters
A mock and a reference hosted from the same contract are aligned by construction, so a reader and an agent see the same surface.
The decision rule
Use the mock cloud for a standalone hosted mock. Use the Hub when the mock and the reference should be hosted together.
This is part of the Powerduck vs WireMock comparison. Next, read the matching comparison.
Comments
Join the discussionNo comments yet. Be the first to comment.