Have you ever wondered if you can use event modeling to understand and document your current system—even if it’s built with traditional CRUD operations and relational databases? The answer is yes! Event modeling is technology- and architecture-agnostic, which means you can apply it to any system.
In this video, I’ll walk you through a simple library management system example and show you how to:
Model information flow in an existing system
Map events directly to your database tables
Use Miro’s event modeling toolkit to connect events to table schemas
Track how each event populates specific columns (like ISBN, title, or status)
Get a transparent view of how information flows and evolves over time
By the end, you’ll see how event modeling not only helps document event-driven systems, but also makes traditional relational systems more transparent and easier to understand.
⏱️ Timestamps
0:00 – Why event modeling works for any system
0:16 – Modeling information flow without event sourcing
0:29 – Example: Library management system
1:20 – Mapping events to relational tables
2:32 – Populating table schemas with event data
3:50 – Handling additional fields like status
4:46 – Classic view: See which events update which columns
5:31 – Why this method works for documenting traditional systems
If you want to make your existing systems more transparent, understandable, and future-proof, event modeling is the way to go.