Three years ago, I was struggling to keep track of the events and services in a growing event-driven system at an organization I was working at.
No events were documented, and we fell into a big ball of mud... (easy to do! with event architecture IMO)
2021 Christmas I started building EventCatalog as a weekend project to solve that — and it slowly grew into something much bigger.
EventCatalog is now an open source tool to document and visualize event-driven architectures — events, services, domains, diagrams — all in one place.
What started as a personal tool has turned into a community project used by teams to bring clarity to complex EDA systems. I’ve been working on it solo for 3 years, refining it with real users, adding governance features, imports/exports, and now even a Studio for visual modeling.
Three years ago, I was struggling to keep track of the events and services in a growing event-driven system at an organization I was working at.
No events were documented, and we fell into a big ball of mud... (easy to do! with event architecture IMO)
2021 Christmas I started building EventCatalog as a weekend project to solve that — and it slowly grew into something much bigger.
EventCatalog is now an open source tool to document and visualize event-driven architectures — events, services, domains, diagrams — all in one place.
What started as a personal tool has turned into a community project used by teams to bring clarity to complex EDA systems. I’ve been working on it solo for 3 years, refining it with real users, adding governance features, imports/exports, and now even a Studio for visual modeling.
GitHub: https://github.com/event-catalog/eventcatalog
Demo / Docs: https://eventcatalog.dev
If you work with event-driven systems, I’d love your thoughts:
How do you document your events/services today?
What’s still painful or missing in tools like this?
This project has been a long journey — now I’m opening it up to more feedback and ideas from the HN community!
Thanks for reading!