4 posts tagged with "Visualiser"

A flow tells the story of a business process. A shopper checks out, the cart is priced, payment is authorized, the order is created, and the customer gets a confirmation.

Flows in EventCatalog have always been good at showing the steps. But once a team has the steps, the next questions are almost always about ownership:

• Which teams are involved in this process?
• Where does it cross from one domain into another?
• Which systems have to work together for this to succeed?

Those questions matter because every boundary in a flow is a handoff. It's a contract between two teams, a dependency someone has to coordinate, and usually the place where things break. Until now, you had to work that out by clicking through each step.

In EventCatalog v5, you can group any flow by domain, system or team. You see the boundaries straight away, and you don't need to change a single line of your flows.

Different people ask different questions of the same architecture.

A head of engineering wants to know which domains depend on each other. An architect wants to see the systems inside a domain and how they connect. An engineer about to change a service wants to see every message it sends and receives.

Until now, EventCatalog answered those questions with different pages. A domain had a System Diagram and a Resource Diagram. A system had a Context Diagram and a Resource Diagram. Services had a Data Dependency Graph, and there was a Domain Integration Map that most people never found. They were useful, but you had to know which one to open.

In EventCatalog v5, every domain and system has one diagram with three levels of detail. Start with the big picture, then zoom in until you can see the messages.

EventCatalog 3.28.1 adds custom icons to every resource type. Set styles.icon in any frontmatter and that icon appears across your entire catalog: visualiser nodes, sidebar navigation, documentation headers, and search results.

EventCatalog 3.28.0 adds a small but useful flag to services: externalSystem: true. Set it on any service (like Stripe, Twilio, or Snowflake) and EventCatalog will treat it as a third-party dependency rather than something your team owns.