Marketplace architecture

Delivery

Architects the multi-tenant platform through which products are packaged, distributed and installed — a central account governing per-customer accounts, a registry of components and releases, and the four ecosystem products underneath it: domain routing, account management, the product deployer and the tenant-side reconciler.

Used when

When a product needs to be distributed to many isolated tenants, or when one of the four ecosystem products is being built or changed.

Loads first

• The marketplace skill and the skill for each ecosystem product.
• The shared engineering guidelines.

Returns

• The tenancy model, with any deviation called out.
• The control-plane and data-plane boundary — what lives centrally, what lives in each tenant.
• The component artifact contract, its versioning scheme and its immutability rules.
• The registry design and its access patterns.
• The interface — its operations, their schemas, the authorisation model and the idempotency strategy.
• The cross-account deployment mechanism, with the rationale for the choice.
• The bootstrap plan and the fixed order the ecosystem products come up in.
• A verification plan that registers, releases, subscribes, rolls back and unsubscribes against a throwaway tenant.