Solution:Agile Dead Trees Paslangella: Difference between revisions
From architectural katas solutions
Paslangella (talk | contribs) No edit summary |
Paslangella (talk | contribs) No edit summary |
||
| Line 3: | Line 3: | ||
==Assumptions== | ==Assumptions== | ||
*The customer already has | *The customer already has CMS and E-Commerce systems in place | ||
*The CMS and E-Commerce systems are able to interact with the message BUS | |||
==Context Diagram== | ==Context Diagram== | ||
| Line 10: | Line 11: | ||
==Container Diagram for the Notification System== | ==Container Diagram for the Notification System== | ||
Depicted below there are the Containers for the Notification System. | |||
[[File:Agile Dead Trees Paslangella Notification System Container Diagram.jpg|600px]] | [[File:Agile Dead Trees Paslangella Notification System Container Diagram.jpg|600px]] | ||
Revision as of 13:56, 5 August 2022
Summary
A publisher wants to unify its authoring CMS and customer store experience.
Assumptions
- The customer already has CMS and E-Commerce systems in place
- The CMS and E-Commerce systems are able to interact with the message BUS
Context Diagram
The Context Diagram depicts the systems involved in the integration. In particular, it will be needed to implement the Notification Service that will be used to notify when a new book version will be available to the Customers. The Customers can go to the E-Commerce platform to Download the new book version.
Container Diagram for the Notification System
Depicted below there are the Containers for the Notification System.
Container Diagram for the Book Authoring System
Depicted below there are the Containers for the Book Authoring System. It will be needed to add the Book publishing service that will be used to interact with the notification service when a new version of a book is published.
