ayan.poddar/eShopOnContainers
1
0
Fork 0
Code Issues Pull Requests Projects Releases Wiki Activity

Updated Roadmap and Milestones for future releases (markdown)

Cesar De la Torre 2017-02-08 11:12:09 -08:00
parent 6e8bfe7fab
commit 4351ce14ec
1 changed files with 5 additions and 5 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

10
Roadmap-and-Milestones-for-future-releases.md

@ -11,11 +11,11 @@ Business-Exceptions + Generic-Exception-Handler (ExceptionHandlerHandler)
- Implement "Idempotent" updates at microservices, so the same update (like a Payment or OrderCreation) cannot be executed multiple times. Server must implement operations idempotently. An operation is idempotent if it gets the same result when performed multiple times. Implementing idempotency is domain-specific.
- INTEGRATION EVENTS with Event-Bus implementations: Implement Event-Driven communication between microservices/containers based on Event-Bus interfaces and two implementation:
1. Standalone Pub/Subs messaging implementation based on an out-of-proc RabbitMQ Container
2. Azure-attached implementation based on Azure Service Bus using Topics for Pub/Subs
Two scenarios to implement:
- Simple (higher priority): Change Product info in the Catalog and update that in the Orders (all, except the price)
- Complex: Events propagating Order's states changes related to the Order-Process SAGA (InProcess, Paid, Handling, Shipped, Canceled if timeout because it was not paid, etc.) - Scenario to be discussed/defined
.1. Standalone Pub/Subs messaging implementation based on an out-of-proc RabbitMQ Container
.2. Azure-attached implementation based on Azure Service Bus using Topics for Pub/Subs
Two scenarios to implement in the app:
. Simple (higher priority): Change Product info (name, image URL, etc.) in the Catalog and update that in the existing Orders and Baskets (all, except the price)
. Complex: Events propagating Order's states changes related to the Order-Process SAGA (InProcess, Paid, Handling, Shipped, Canceled if timeout because it was not paid, etc.) - Scenario to be discussed/defined
- DOMAIN EVENTS: Implement Domain Events which is related but not the same as integration events for inter-microservice-communication. Domain Events are initially intended to be used within a specific microservice's Domain, as communicating state changes between Aggregates, although they could derive to Integration Events if what happened in a microservice's domain should impact other additional microservices.
See discussion: