-
1/ Visual Artifacts are so necessary to communicate information and change. In a world full of microservices, it's so hard to know their responsibilities and to whom they talk (some monitoring tooling does that for you). At @CreditasTech, we use the next building blocks👇Permalink On twitter.com
♻️ 1 Retweets ❤️ 5 Favorites Mood -1 🙁
-
2/ We use the DDD Subdomain Categories to bring the importance of each microservice. We need to know what's more important by a simple color categorization.Permalink On twitter.com
-
3/ - 🟢 Core Domain. Our business differentiator ⭐️ - 🔵 Supportive Subdomain. Either internal or external but it exists to support our core business - 🟣 Generic Subdomain. Probably an external system. - ⚪️ Technical Service. A technical component like KongPermalink On twitter.com
-
4/ We briefly expose what they do in terms of: - 🔵Entry Points. Controllers / Listeners - 🟢Use Cases. What actually does. - 🟡Entities. The main Entities it manages. - 🟠Events. Domain Events it emits.Permalink On twitter.com
-
5/ We connect the services using either: - Continuous Line. Sync communication - Dashed Line. Async communicationOn twitter.com
-
6/ With these building blogs, we can get a full picture of our microservices, what they do, who they interact with and their responsibilities And you? How do you map your microservices in a way that you can share visually what they do, and how do you plan to introduce change? 🤔Permalink On twitter.com
-
7/ Here a small example of connecting the servicesPermalink On twitter.com
