3 posts tagged with "Architecture"

Every team I've talked to has the same problem. The architecture lives in one place and the diagrams live in another. The documentation is accurate as of six months ago. The Miro board from the last event storming session doesn't match what's actually running.

Today I'm releasing the EventCatalog Miro App v2, a Miro app that turns your EventCatalog documentation into interactive, collaborative design artifacts — and brings your design decisions back into the catalog when you're done.

Your real architecture, imported into Miro with relationships intact

As event-driven architectures scale, an invisible problem emerges: who is producing what, and who is consuming it? A service starts consuming your OrderPlaced event. No ticket. No Slack message. No email. You find out weeks later when something breaks downstream.

At scale, you need governance over these relationships. You need to know when dependencies change, who is affected, and ideally, before it reaches production.

EventCatalog already gives you auto-generated visualizations: Entity Maps, Interaction Maps, and domain views that update as your catalog changes. These are great for understanding relationships between your resources.

But sometimes you need your own diagrams. Target architecture plans. Event storming results. Sequence flows from Miro. C4 diagrams from IcePanel. The stuff that lives in scattered boards, Confluence pages, or that folder someone created two years ago.

EventCatalog 3.3.0 lets you bring those diagrams to your documentation.

Your custom diagrams are now first-class, versioned resources in your catalog. Bring them in from any tool, version them, link them to your domains and services, and even ask AI about them.