Open host service (published language)
An upstream context offers one documented, stable protocol for all consumers instead of a custom integration for each, often with a published data format.
When many systems need the same capability, building a one-off integration for each one does not scale. An open host service exposes the capability once, as a public API, event stream or, for AI assistants, an MCP server, and every consumer uses the same contract. The published language is the shared format of that contract: a documented schema, an industry standard or a set of domain events.
It is how a migrated capability, such as bookings, becomes a building block other products plug into. The contract has to be designed for strangers: versioned (see API versioning), documented and free of internal names. Both patterns are in the Evans DDD Reference and appear as labels on a context map.
Sources
- Domain Language: DDD Reference domainlanguage.com
Related terms
- Context map (DDD): A diagram of the bounded contexts in a system and the kind of relationship between each pair: who depends on whom and how models are translated.
- API versioning: Giving an API contract explicit versions so consumers can upgrade on their own schedule, and retiring old versions with notice.
- Domain event: A fact the business cares about, named in the past tense (“visit booked”), that other parts of the system can react to without being called directly.
- MCP (Model Context Protocol): An open protocol for plugging tools and data into AI apps: write a server once, use it from any client.
