LinkedIn·Monday, 24 August 2026·2d ago

What is the best boundary choice when publishing capabilities? Daniel Kocot just published a great article about the difference between…

Kristof Van Tomme

Open Source Developer Portals & API Docs

What is the best boundary choice when publishing capabilities? Daniel Kocot just published a great article about the difference between deliberate and (natural) DDD boundary choice when creating APIs. He makes the case that your organisation's historical domain model should not define your interface architecture. That otherwise you will expose your customers to your internal complexity and create a suboptimal Developer eXperience. Last week we did an article about how to publish MCP servers on developer portals, where we made the case that roughly there are 3 architectures depending on how you package capabilities. Combined with Daniel's insights that really gives food for thought when you are translating your existing API landscape 1-on-1 into MCP servers. MCP gives you another chance to rethink your capability bundles. While hosts can compose capabilities as needed, taking the easy choice will increase transaction costs, just like with APIs. #API #capabilities #Developer_Experience #MCP DDD Does Not Define Your API Boundaries https://www.linkedin.com/pulse/ddd-does-define-your-api-boundaries-daniel-kocot-nugfe?trackingId=OS9xqNtjYQvk1CJCpRN8Fw%3D%3D