Application violation in a limited context

How do you plan and share your application in a limited context? On the one hand, it is very convenient, having all this interchanges, but, on the other hand, too much detail can lead to a very cumbersome development. Where is this thin line? What factors do you consider when designing your limited contexts and context maps? Can they be technical, strategic?

In many examples, you see an e-commerce application as a set of limited contexts: catalog, shopping, billing, delivery, etc.

Where do they come from?

+4
source share
3 answers

Technical, definitely not ...

Event Storming? , ...

- , , , : -

, ( eCommerce, - : , ... ... , Ubiguitous ), (- )

+2

, .

, , .
(/) "", , "" Renters, :

  • IdentityAndAccessContext ( , ..)
  • MovieRentalContext ( , )

- .

+1

. , , ( ). .

+1
source

All Articles