Many teams use diagrams to capture their architecture, event modeling, and event storming sessions, often these artifacts are left in Miro, Lucid, or Draw.io and can be difficult to find when you need them.
EventCatalog now supports embedding these diagrams into your documentation, making it easier to collaborate and get more value from your diagrams.
We have introduced new components which can be used in your domains, services, and messages:
We have launched our first version of the EventCatalog Miro plugin. This plugin allows you to bring EventCatalog into Miro, making it easier to collaborate and get more value from your diagrams.
You can import all your resources into Miro, including services, messages, and more. Then drag these resources into your diagrams.
Miro Plugin - Roadmap
The Miro Plugin is open source and can be found on GitHub. The plugin is read-only for now, but we are working on adding edit capabilities soon.
The plugin is still in early stages and we would love to hear your feedback.
To get started you can read more about the Miro plugin and how to use it.
The Lucid component allows you to embed Lucid diagrams into your documentation. These diagrams can be embedded into your domains, services, messages and custom documentation pages.
The <DrawIO /> component allows you to embed Draw.io diagrams into your documentation. These diagrams can be embedded into your domains, services, messages and custom documentation pages.
Miro, Lucid, and Draw.io are all great tools for capturing and sharing diagrams. With our new embedding feature, you can now bring those diagrams directly into your EventCatalog documentation—making it easier to collaborate, share context, and get more value from your visual workflows.
If you have any feedback or suggestions, please open an issue and we will look into it.
Our community has grown to over 1,100 members and continues to expand! If you haven’t already, join us on Discord and be part of the conversation.
Many teams turn to Miro to brainstorm, map out, and document their architecture. In the world of event-driven systems, techniques like Event Modeling and Event Storming are especially popular. Now, you can embed your Miro boards directly into your documentation—making it easier to collaborate, share insights with your team, and get more lasting value from your diagrams and workshops.
Introducing the new Miro component — now you can seamlessly embed Miro boards into any EventCatalog page, from domains and services to messages and custom documentation. This makes it easier to bring your architecture diagrams, event modeling, and brainstorming sessions into context, keeping everything in one place and driving better alignment across teams.
Need more space to explore your diagrams? Clicking the full-screen icon on an embedded Miro board will open it in a new tab, giving your team a larger canvas to work with. If you have edit permissions, you can collaborate in real time—perfect for live sessions and ongoing updates.
Many teams use Miro to capture architecture decisions, event modeling, and event storming sessions. With our new Miro embedding feature, you can now bring those boards directly into your EventCatalog documentation—making it easier to collaborate, share context, and get more value from your visual workflows.
Check out the docs and props to get started and start enhancing your documentation today.
We’d love to hear your thoughts—feel free to open an issue with any feedback or suggestions.
Our community has grown to over 1,100 members and continues to expand! If you haven’t already, join us on Discord and be part of the conversation.
Excited to see what you build with this new feature!
I’m excited to share that EventCatalog 2.33.0 is now available. This release introduces the new EventCatalog Custom Documentation feature. This feature allows you to bring your own documentation to EventCatalog.
In the past EventCatalog has been focused on documenting your domains, services and messages. This has been great for EventCatalog users, but many people wanted the ability to extend the documentation capabilities of EventCatalog.
This is why we are introducing the new EventCatalog Custom Documentation feature. This feature allows you to bring your own documentation to EventCatalog.
All your custom documentation is stored in the /docs folder, and can be organized in anyway you want.
You then configure the sidebar in your eventcatalog.config.js file to configure your sidebar.
You can read the documentation here to get started and start building your own documentation.
You can start adding your custom documentation to your EventCatalog in minutes. You can read the documentation here to get started and start building your own documentation.
Welcome to the monthly update for EventCatalog, here you can find what’s next, how to get started, and what’s coming next.
EventCatalog community continues to grow ❤️, now we have 1,097 Discord members, 2.1k Stars on GitHub, 820 new catalogs have been created in March and 11.2k catalogs built into production. EventCatalog continues to grow every month, and we are on track with open source sustainability.
EventCatalog sponsors OSO and Gravitee continue their sponsorship for the project (thank you!) 🙏. This sponsorship helps my goal towards open source sustainability. EventCatalog is free to use and open source, if you want to support the project checkout the tiers on GitHub or contact me directly at dave@eventcatalog.dev , I really appreciate any support ❤️
In March we introduced tiered pricing, EventCatalog MCP Server, Custom nodes to Flows, New Navigation Bar, More customization options, new components and many features were introduced.
In March we introduced tiered pricing to EventCatalog, these plans include, Community Edition, Starter Plan, Scale Plan and Enterprise Plan, our aim is to help companies when they need it, and scale governance and documentation with them along their journey.
After years of working with event-driven architecture, I’ve come to see it as a journey that many companies undertake. It often begins with simple broker-based pub/sub patterns, which are easy to understand and manage early on. At this stage, governance isn't a major concern. But as the architecture scales across the organization, complexity grows—and with it, the need for stronger governance and structure becomes increasingly clear.
When you go from 10 events to 1000s of events, maintenance becomes hard and people fall into the same common mistakes around versioning strategy, lack of documentation, and wasted time trying to figure all this out. (I have a talk about all this!)
The new EventCatalog plans are designed to support you at every stage of your event-driven journey, scaling governance and documentation as your needs grow.
Begin with the Community edition to get up and running quickly. As your requirements expand, the Start plan offers additional capabilities like custom documentation and conversational architecture insights. When it's time to scale your architecture, the Scale plan introduces automation and advanced features to streamline your workflow. And for organizations operating at mass scale, our Enterprise plan provides the tools and flexibility needed to manage complexity with confidence.
You can find the plans here and features that are included in each tier, if you have any questions feel free to reach out, happy to help.
Architecture pages were released into EventCatalog. This is another way to quickly visualize and understand what messages are doing to and from your services and domains.
The architecture diagrams let you drill down into various different levels of information. Starting at domains, you can click into your services to see detailed information about what messages are sent/received from that service, and finally clicking on the message will take you to the documentation and schema for that message.
Using the filters you can quickly filter by message type, or search for domains, services and messages you are interested in. If you are interested to learn more you can watch the video here or view the demo.
You can now use EventCatalog inside your IDE or any MCP client. This brings a huge amount of value to EventCatalog for your teams and developers. Your team can now talk to your catalog of information in the client of their choice (e.g IDE), and use that context to create code , get schemas or understand their architecture.
Teams waste a huge amount of time trying to find the information they need. In event-driven architectures this problem scales fast. Being able to quickly find producers/consumers, schemas, messages, and context can save a huge amount of time, and now using the MCP server I believe developers can save even more time.
As developers are writing and exploring ideas, they can talk directly to your EventCatalog to get the information they need, and write code based on the context of your architecture.
This is the first release of this feature, and we look to add more value in April.
EventCatalog gives you the ability to document business workflows (EventCatalog Flows). You can use your resource inventory (services and messages) and create business workflows. These workflows can help your organization understand and know what is happening in your architecture.
Flows can be used to help you get more value from EventCatalog. Think of a feature you have, from A to Z, and you want to document what happens and the events, messages, services, external systems that it interacts with. This is what flows help you document.
In March we released the ability to add any custom node to your flow. To give you examples, you can now document schedules, decisions, timers, processors… anything you want!
Using custom nodes you can now document any business flow you want in EventCatalog and embed these flows directly into your documentation using the Flow component.
The new message table component will list all messages in a domain or service on your documentation page and give your users the ability to quickly search for messages they are interested in and filter them by queries, commands or events.
We introduced the idea of Resource Groups, this gives you the ability to document and group resources in EventCatalog in ways that EventCatalog wasn’t to before.
With resource groups you can also define your own documentation sections in your sidebars.
Thanks to our community we now have better search results in EventCatalog. Using the search bar in EventCatalog will now return better results for your users, giving them the ability to quickly find what they need.
AsyncAPI and OpenAPI documents are also added to the search results.
In March we released a new navigation bar option to help organize your documentation. With this new navigation bar you can quickly find the information you need, use custom badges to highlight resources and also view OpenAPI and AsyncAPI specifications.
OpenAPI Generator 5.0.2 is now out. Adding httpMethodsToMessages property to the OpenAPI Generator plugin. Map HTTP methods to message types easier in EventCatalog.
In April we are releasing the ability to add custom documentation to EventCatalog, this gives you the ability to bring your own docs to your catalog (e.g Runbooks, Product pages etc), this gives you flexibility on what you want to document, whilst using EventCatalog components to enhance it. We will also be adding custom docs to EventCatalog Chat and MCP server.
We also want to release the first version of our Schema API. This will let you call EventCatalog as an API to get your schemas, which could be useful for contract testing, validation and much more. We are looking to follow the xRegistry specification for this.
Introducing the ability to add drafts to EventCatalog and letting teams use EventCatalog in early phases of your journey. Documenting your thoughts and getting feedback from your teams.
We are aiming to get the Confluent schema registry plugin released, giving you the ability to pull in schemas from Confluent into EventCatalog.
We are exploring runtime components, giving you the ability to write your own runtime components/blocks on your page to extend the catalog into more personal use cases (e.g self service for producers/consumers, datadog integrations).
We want to spend more time on Event EventCatalog Studio. Giving you the ability to do all of this with a custom UI, and design your EventCatalog.
As normal, things can change but this is the direction we are heading.
If you have any questions or want to join our community of over 1100 people exploring EventCatalog and event-driven architecture feel free to join us!
The vision for EventCatalog is simple; to help companies bring discoverability to their architecture and reduce the time it takes to maintain, understand, and build new features.
We want to build a platform that enables developers to quickly find and understand the information they need, whilst giving architects and business stakeholders the ability to govern their architecture and control the standards of their systems.
Overtime distributed systems become more complex, the need for a governance and a single source of truth for your architecture becomes more important.
We believe EventCatalog is a step in the right direction to help teams achieve this, and today we are happy to share that EventCatalog now supports the Model Context Protocol (MCP), which we believe can help teams save time by finding the information they need directly in their code editor or LLM.
Using the EventCatalog MCP Server you can provide your EventCatalog data to any LLM or AI application that supports the MCP protocol.
Some examples of what you can do with the EventCatalog MCP Server include:
Improved Discoverability - Ask questions about your architecture directly in your code editor or LLM.
Schema Access - Get access to schemas directly in your code editor or LLM and use them to build new features.
Producers and Consumers - Quickly understand who consumes the events you are about to change
Context - Use EventCatalog context to help you build new features, and explore what you already have.
Saving time - Reduce the time it takes to understand, find information you need to maintain or build new features.
In this blog post we will cover what is the MCP protocol and how you can get started with the EventCatalog MCP Server.
MCP is an open protocol that standardizes how applications provide context to LLMs. Think of MCP like a USB-C port for AI applications. Just as USB-C provides a standardized way to connect your devices to various peripherals and accessories, MCP provides a standardized way to connect AI models to different data sources and tools. (MCP Introduction)
The EventCatalog MCP server can be installed on your machine and give you access to your EventCatalog data in your code editor or LLM (MCP Client, e.g Cursor, Windsurf, Claude Desktop).
This can reduce the time it takes to understand and build new features, as you can ask questions about your architecture directly in your code editor or LLM.
Rather than having to search through your code base, trying to find producers and consumers of the event you are about to change, you can ask the EventCatalog MCP server for this information, or maybe you want to know what other events are related to the one you are about to change, or you want to quickly find events based on the feature you want to build.... the possibilities are endless.
We want to reduce the time it takes for developers to understand their architecture and we believe that the EventCatalog MCP server can help you achieve this.
We are excited to announce that EventCatalog now supports the MCP protocol. This is a big step forward for EventCatalog and we are looking forward to seeing what you can build with it.
If you have any questions, please reach out to us on Discord or GitHub.
Welcome to the monthly update for EventCatalog, here you can find what’s next, how to get started, and what’s coming next.
EventCatalog community continues to grow ❤️, now we have 1,030 Discord members, 2k Stars on GitHub, 759 new catalogs have been created in February and 8.5k catalogs built into production. EventCatalog continues with 15-20% growth every month. We are currently on track for open source sustainability in 2025.
EventCatalog sponsors OSO and Gravitee continue their sponsorship for the project (thank you!) 🙏. This sponsorship helps my goal towards open source sustainability. EventCatalog is free to use and open source, if you want to support the project checkout the tiers on GitHub or contact me directly at dave@eventcatalog.dev , I really appreciate any support ❤️
EventCatalog documentation can be automated from any system or broker in the world (using the SDK) or EventCatalog integrations, this cloud platform was designed to give users the ability to trial integrations before deciding to purchase integration licenses.
In the future EventCatalog Cloud will offer hosting, organizations/users, ability to design event-driven architectures (with EventCatalog Studio) and much more.
You can now use natural language to talk to your EventCatalog. This new feature let’s your teams get access to information they need in seconds rather than hours or days.
EventCatalog Chat is a local first, and privacy first AI feature, that runs locally in your browser. No data is shared, which allows you to keep your data private to your organization.
Use cases include:
Ask your catalog what messages you have related to a new feature you want to build
Ask your catalog what messages a service publishes/consumes
Find gaps in your messages or naming conventions in your architecture
Highlight messages that are not following certain conventions
And much more…
EventCatalog Chat is still in beta, and you can access it by enabling it on your catalog and following these instructions. If you want to try it yourself, you can view the demo here (Chrome and Edge browser support only).
LLMS.txt is a proposed standard that helps AI-powered development tools better understand and interact with your documentation. Similar to how robots.txt guides web crawlers, LLMS.txt provides structured information that makes it easier for AI assistants like Claude, ChatGPT, and GitHub Copilot to process your EventCatalog documentation.
Using the new TREE_VIEW setting the sidebar will now render your catalog resources in a nested structure (which mirrors your directory structure). This can be particularly useful for large catalogs
Hopefully these new examples can help you understand how EventCatalog works with our integrations, and how you can get value from automating your documentation, or scaling your documentation in your organization using EventCatalog federation.
We continue to work with companies around the world helping them lay the foundations for their event-driven architecture governance. This includes best practices, patterns and diving deep into their problems.
If this is something you would be interested in, please get in touch. Happy to explore how we can help.
EventCatalog has huge potential to help people govern their event-driven architecture. Surrounding this includes a wide range of tools and value it can unlock for you and your teams. Our vision in 2025 is make this happen, and here is a diagram of where we are heading.
In March we hope to improve the visualizer, add the ability to add events to domains, and visualize integration events between domains. We aim to get EventCatalog Studio in front of the first batch of early beta users to help them design and edit their catalogs.
If you have any questions or want to join our community of over 1000 people exploring EventCatalog and event-driven architecture feel free to join us!
I’m excited to share that EventCatalog 2.24.3 is now available. This release introduces the new EventCatalog Chat feature (in beta). This feature allows you to understand your architecture through natural conversation.
Here are some examples of how EventCatalog Chat can help you understand your architecture:
Building a new feature? Want to know what messages you already have?
Don’t know what messages your company has already? Ask the catalog, get insights in seconds, not days.
EventCatalog will point in you in the right location, with links directly to your messages, services and domains.
Want to know the impact of breaking changes?
EventCatalog knows who produces/consumes messages (powered by AsyncAPI, OpenAPI, or any broker in the world). That chat interface can tell you in seconds the impact of your changes.
Want to find gaps in your event architecture?
Ask your catalog what events are missing, it can help suggest some naming conventions for you and get you started.
Talk to enterprise architecture?
Save time across your organization. Use EventCatalog Federation to build a single source of truth for your event-driven architecture
Use EventCatalog Chat to talk to large architectures across your organization.
Talk to any broker in the world
EventCatalog is tech agnostic, integrate with any system you want either using our integrations or by using the EventCatalog SDK.
If you are interested in bringing your own models (API Keys) (OpenAI, Anthropic, etc) let us know as this is on our roadmap, if more folks vote we can prioritize the feature.
When event-driven architectures get to a certain size it becomes difficult to know who owns a service, event, query or command. This is why we are introducing the EventCatalog Directory.
Using the EventCatalog Directory you can quickly find users or teams by services, events, queries and commands that they own. If you need to quickly find out who owns a service, event, query or command you can use the directory to find them.
Previously the users and teams were listed in the documentation sidebar. We have now moved them to their own directory page keeping the documentation sidebar focused on your domains, services and messages in your catalog. To upgrade to the new version you can run the following command:
When you add a user or team as owners of your domains, services, events, queries and commands they will appear in the directory and on your documentation pages.
Each user and team has their own page in EventCatalog. This page helps you understand more information about the owner and quickly see what services, events, queries and commands they own.
As your event-driven architecture grows, the EventCatalog Directory will become more useful. The EventCatalog Directory can be used to help your developers, architects and stakeholders understand the ownership of your event-driven architecture.
Each team or user in EventCatalog has their own page, this page helps you understand more information about the owner and quickly see what services, events, queries and commands they own.
EventCatalog Directory works well with the EventCatalog Federation plugin. Federation allows you to pull in users and teams from other catalogs into your main catalog, this means you can have a single source of truth for your event-driven architecture.
There is much more we want to do here, and we are just getting started.
EventCatalog has been another great month for EventCatalog with almost 2k stars on GitHub, and 1000 Discord members. Our project continues to grow about 10/15% every month in usage.
To help keep the project sustainable and open source we have now introduced license keys for our plugins. All our plugins were dual licensed, but did not require any license key to run or use them. This small change allows us to offer a better experience for our users and a sustainable project.
All plugins will now have a 14 day trial period (you can extend contacting us), after which you will need to purchase a license key to continue using the plugin.
January was slightly a slow month in terms of maintenance and features as I was focused on EventCatalog Cloud, and talks for NDC and FOSDEM. These events were great and I met a lot of new people, and got to catch up with old friends.
I am looking forward to February, we have a lot of great features and quality of life improvements planned.
If you want to join us on this journey feel free to join our Discord community, and if you want to sponsor the project you can do so here.
Welcome to the monthly update for EventCatalog, here you can find what’s next, how to get started, and what’s coming next.
EventCatalog community continues to grow ❤️, now we have 937 Discord members, 1.9k Stars on GitHub, we hit over 1000 pull requests into the project, 423 new Catalogs have been created in December and over 5,000 catalogs built into production this month. EventCatalog got a great shoutout at re:Invent 2024, and the project continues with 15-20% growth every month.
EventCatalog sponsors OSO and Gravitee continue their sponsorship for the project (thank you!) 🙏.
Sponsorships help our goal towards open source sustainability. EventCatalog is free to use and open source, if you want to support the project checkout the tiers on GitHub or contact me directly at dave@eventcatalog.dev , I really appreciate any support ❤️
In December we introduced the ability to filter resources by custom badges, ability to document Ubiquitous Language, over 200,000 icons support with Mermaid v11, new tab components, 80% increased build times and we launched EventCatalog Federation.
In this blog post we will dive deeper into features that were released in December, why they were built and how they can help you govern your architectures. At the end of the blog post I will share a personal update and what’s planned for January 2025.
In December we launched our first version of EventCatalog Federation. EventCatalog federation let’s you unify your documentation across your organization into one view.
EventCatalog Federation takes many catalogs and merges them into one view for your organization.
This let’s your teams keep their own documentation, schemas and spec files close to their code, and merge this information into one view for the organization.
Give your architects and company the ability to get a holistic view of the whole architecture
See ownership of domains, services and messages and contact them
Let your teams quickly find events, schemas and specs they want to start consuming
Let’s your team own their own documentation, focusing on their domain and service
Our vision with EventCatalog is to bring discoverability to architectures for teams saving them time from discovering a message to the implementation phase. We believe EventCatalog Federation can help scale EventCatalog within your teams and business.
Event-driven architecture and domain-driven design work very well together (see visual here). Many teams are embracing domain-driven design practices whilst building their event-driven architecture. Part of this process includes understanding and defining a ubiquitous language.
Ubiquitous language is the language (terms) you use within a particular domain. For example a Policy in a Underwriter Domain might be completely different to a Policy in a User Domain.
This language often get’s translated into code/models within your architecture, but the meaning of these terms/words can often get lost or confused.
The EventCatalog ubiquitous language dictionary gives you the ability to document your domains language with a simple markdown file. These definitions will get rendered into EventCatalog and can help your teams understand terms used within your architectures domain, helping with any confusion that may occur.
The ubiquitous language dictionary is powered by markdown files, this let’s you document short or large descriptions of your language and users can quickly filter and search for terms in your domain.
To get started you need to create a ubiquitous-language.mdx in your domain folder, and then EventCatalog will render this for your users. To understand more and get started you can read the documentation here.
We have now added the ability to search and filter by badges. Badges are custom tags you can add to your resources in EventCatalog, this let’s you add any metadata you like to your domains, services, flows and messages.
If you want to enable quick filtering/search based on custom information you can use badge filters to do this.
EventCatalog let’s you use mermaid code blocks in all resources, this is handy if you want to provide extra visualisations or information about your domains, services or messages.
In December we updated Mermaid to V11. This gives you the ability to render Architecture Diagrams and now supports over 200,000 icons for your diagrams.
You can also render Block Diagrams, C4 Diagrams, Mind maps and much more (see examples).
Mermaid can be a great way to provide additional information for your developers and teams in EventCatalog. To get started you can read our documentation on how to use mermaid in EventCatalog.
In November we started working on EventCatalog Studio. This visual editor for EventCatalog, letting you quickly explore, experiment and design your architecture with a drag and drop interface. The vision is to go from design to implementation faster than ever.
We continue to work on this in Q1 2025, if you would like to sign up to the beta you can sign up here. Or if you want to understand how it can help your teams feel free to reach out to us at hello@eventcatalog.dev .
Our vision is to help companies bring discoverability to their event-driven architecture through open source community and software. The project usage is growing 15-20% a month and we aim to at least double this in 2025.
Our aim is to work backwards from the community and EventCatalog users to define a public roadmap and continue to grow our community. The community and open source is the core of the project and we want to do everything we can to help maintain this and grow.
We will focus on making a welcoming community, have community meetings and create a place where people can learn, explore and help each other.
We have started to work with companies to help them govern their event-driven architectures and make best use of EventCatalog. If you want to work with us reach out at hello@eventcatalog.dev , we would love to help you understand how EventCatalog can help your organization, provide value and solve problems you may be facing.
We will continue to explore project sponsors. This helps keep the core of the project free and open source. If you or your company would like to sponsor our project we would love to connect. You can reach out at hello@eventcatalog.dev and we can share details with you on what you can get from sponsoring the project. We currently have 2 sponsors, our 2025 goal is to double this.
We will continue to grow our integration platform. This includes working with cloud providers, broker providers and companies to integrate EventCatalog into their eco-system. If you would to see an integration or get help building a custom integration we can help.
We will continue to explore the EventCatalog eco system. Looking at tools like EventCatalog Studio and other tools that users may find useful. We believe that EventCatalog can had a huge amounts of value to businesses and teams, and we are just starting.
With the EventCatalog ecosystem we believe we can save teams time and money and get them building and documenting event-driven architectures faster than ever.
We are excited for what 2025 has in store for EventCatalog, we have a lot of ideas and plans to help grow the project and community. We are looking forward to working with you and your teams to help you document and govern your event-driven architectures.
If you have any questions or feedback please reach out to us at hello@eventcatalog.dev and we can help you get started.
In 2024 we have seen a lot of companies and teams adopting EventCatalog. We have seen teams use EventCatalog to document their event-driven architectures and microservices.
Many teams are using EventCatalog as a single source of truth for their domains, services and messages . This gives organizations a single source of truth for their documentation.
EventCatalog is helping developers, architects and business stakeholders understand their architectures and quickly find the information they need.
Whilst speaking to our community we have learned that many teams want the ability to keep their documentation close to their code and still continue to have the single source of truth for their organization.
EventCatalog Federation allows your teams to have their own EventCatalog, stub out dependencies and provide an ability to merge multiple catalogs into one main catalog.
This allows your teams to keep their documentation close to their code, store their documentation in git whilst continuing to provide value to the organization.
Your teams own their own documentation, domains, services and messages (all optional). This allows your teams to focus, document what they are doing and what they are consuming.
Once teams commit their documentation to their repository, they can run the federation generator to merge their documentation into a main catalog.
This main catalog provides the organization with a single source of truth for the entire architecture.
Using the federation generator you can specify the source repository to pull from, the branch to pull from, the files to copy from the source repository to your main catalog and if you want to override any conflicts (last-write-wins).
Merging many catalogs into one provides your developers, architects and business stakeholders with a single source of truth for your organization.
The single source of truth lets you see the entire architecture of your organization, and provides a way to understand the dependencies between your teams.
Developers can quickly understand and search for the information they need, and business stakeholders can understand the entire architecture of the organization and start to define business processes (flows) for EventCatalog.
This allows your teams to keep their documentation close to their code, store their documentation in git whilst continuing to provide value to the organization.
We are excited to see what you build with EventCatalog Federation and we are looking forward to seeing the EventCatalog community grow in 2025.
If you have any questions or feedback, please let us know in the EventCatalog Discord.
In this blog post we will dive deeper into features that were released in November, why they were built and how they can help you govern your architectures. At the end of the blog post I will share a personal update and what’s planned for December.
EventCatalog community continues to grow ❤️, now we have 890 Discord members, 409 new Catalogs have been created in November and over 4,000 catalogs built into production this month.
EventCatalog is on track to hit 1.9k stars in November, and a shout out to Carlos Rodrigues and Omid Eidivandi for their support with the project and helping with issues, and community feedback ❤️.
EventCatalog got a new gold sponsor from OSO and Gravitee continue their sponsorship (thank you!) 🙏. This sponsorship helps my goal towards open source sustainability.
EventCatalog is free to use and open source, if you want to support the project checkout the tiers on GitHub or contact me directly at dave@eventcatalog.dev , we appreciate any support to help project sustainability ❤️
EventCatalog is proving to be a great tool to help companies govern and document their event-driven architecture. It’s great to see the project, usage and the community grow. Although this is great for folks that have event-driven architectures to document, we still feel there is a pain point when designing your event-driven architecture.
We feel there is a gap between design to implementation with event-driven architectures.
Many teams use whiteboards to design and explore their event-driven architecture (in person or virtual). During this process many discussions and ideas are captured but lost. Also there is an increasing effort to go from initial design to implementation. We believe there must be better way.
EventCatalog Studio is a visual designer for event-driven architectures. EventCatalog Studio can sync with your local EventCatalog, and provide you with an editing experience, ability to collaborate with your teams, experiment ,and create draft designs to get feedback.
With EventCatalog Studio you can design new architectures, draft new ideas, design and explore your schemas, ask questions about your architecture, and much more. Everything is mapped to your EventCatalog.
EventCatalog Studio let’s you walk away from your white board sessions with something tangible, schemas to get your started and code models to help.
In EventCatalog a channel represents the organization and transmission of messages.
Channels in EventCatalog describe how a messages transport between producers and consumers.
Documenting channels in EventCatalog gives your team deeper understand of how your messages are transmitted between producers and consumers, what broker they use and any other information you may find useful.
As EventCatalog is technology agnostic this means you can document any channel and protocol you like including http, amqp, eventbridge, googlepubsub, kafka, mercure, nats, pulsar, redis, sns, solace, sqs and ws (websockets).
You can now simulate messages in the EventCatalog visualizer. This new feature let’s you quickly see what type of events are flowing between your services.
To turn on the feature, use the Visualizer Settings and click Simulate Messages.
This is the first version of message simulation, ideas we have is the ability to define frequency flow in your documentation to help your teams understand how busy messages are, and even connecting this to live systems. If you have any ideas or requests please join Discord and let us know.
Sometimes your service will send and receive the same message, previously in EventCatalog this was not possible, but we are happy to share that EventCatalog now supports this.
When the service sends and receives the same message, EventCatalog visualiser will now represent this.
--- id: OrderService ...# other service frontmatter receives: # id of the message this service receives -id: PaymentProcessed sends: # id of the message this service sends -id: PaymentProcessed --- <!-- Markdown contents...-->
In November we have been working with companies to help them understand the importance of governance with event-driven architecture and getting them started.
We offer a range of support including internal talks, internal workshops, and hands on catalog builds.
If you are interested in working with us you can reach out on LinkedIn or email at hello@eventcatalog.dev
Want to learn more about event-driven architectures?
We have created free resources for you to dive deeper into event-driven architectures called EDA Visuals. EDA visuals are designs I have made with extra resources. You can view them and download the book for free!
In December we will be continuing the work for EventCatalog Studio and getting an initial beta version out. If you want to keep up to date and get access you can sign up here.
We will continue to review feature requests and work backwards from the community. If you have any feature requests, ideas or bugs please let us know on Discord.
Towards the end of the month we will be taking time off to recharge and focus on what’s next for 2025. I feel EventCatalog has a huge roadmap and vision ahead and we are only just getting started ❤️.
October has been a busy month for EventCatalog. The community has grown from 800 Discord members to 856, with 360 new Catalogs created and over 120 organizations actively using EventCatalog.
EventCatalog got a new gold sponsor Gravitee and Hookdeck continues their sponsorship 🙏, this is a great step towards open source sustainability. If you would like to sponsor the project you can check out the tiers on GitHub or contact me directly at dave@eventcatalog.dev.
In many distributed architectures, domains and services communicate through different types of messages, typically categorized as events, commands, and queries.
EventCatalog now includes support for documenting queries, allowing you to clearly outline which queries a service accepts and which it invokes. Queries are often seen in protocols such as HTTP and gRPC.
September 2024 has been a great month for EventCatalog. In this blog post I want to highlight some growth and new features you can start using with EventCatalog.
It’s been a couple of months since I left my full time job at AWS to pursue my passion for event-driven architecture (EventCatalog) and cloud computing (Wing). I wanted to share an update on the exciting changes we rolled out for EventCatalog in August, it's been a busy month.
EventCatalog 2.5.0 is out now! This release includes the new resource flows, visualizer improvements, and various bug fixes.
This release includes the following highlights:
⭐️ Document business features and workflows with the new content type "Flows"
I'm excited to announce the release of the new JavaScript/TypeScript EventCatalog SDK. This SDK is designed to help users programmatically interact with their EventCatalogs, streamlining the process of managing event-driven architectures.
Event-driven architectures share a common challenge: their complexity can quickly escalate as more domains, services, and messages are added.
As business requirements evolve and teams adapt, governing and understanding this distributed architecture becomes increasingly difficult. What begins as a straightforward system often transforms into a complex structure with minimal documentation and discoverability, leaving most people struggling to comprehend it (I share my thoughts on EDA complexity in this GOTO EDA Day 2024 keynote).
In January 2022 EventCatalog v1 was launched to help bring discoverability and documentation to event-driven architectures. Since its inception, EventCatalog has seen over 13,000 catalogs created, attracted 45 contributors, grown a community of more than 600 members on Discord and was added to Thoughtworks Technology Radar.
The growing popularity of EventCatalog in recent years highlights the challenges of complexity in building event-driven architectures. It also highlights the importance of discoverability and documentation. That's why I'm excited to announce the release of EventCatalog v2.
;
;