Ubiquitous Language By David Boyne

Ubiquitous Language By David Boyne

Ubiquitous Language

It can be time consuming or even frustrating when teams within an organisation are using terms to mean different things depending on the domain. For example a “policy” within one team could mean something completely different within another…. This leads to mental translations of models/business terms and can lead to confusion and assumptions.

Having a “Ubiquitous Language” means parties that communicate between each other speak in the same language. Define standards for terms, share them with each other and use them to describe business domain.

This is not directly associated to “event-driven architectures” but domain driven design plays a huge part in EDA. Having a shared language can help you name events, boundaries and build your EDA applications.

Extra Resources

Want to work together?

If you're interested in collaborating, I offer consulting, training, and workshops. I can support you throughout your event-driven architecture journey, from design to implementation. Feel free to reach out to discuss how we can work together, or explore my services on EventCatalog.

Download EDA Visuals

Join over 13,000 others learning EDA and download all the EDA visuals directly to your computer. This document updates everytime a new visual is added so make sure you come back to get the latest.

Download now →
Diagrams and thoughts by @boyney123 to help you learn.