ddd-crew / context-mapping Goto Github PK
View Code? Open in Web Editor NEWLicense: Creative Commons Attribution Share Alike 4.0 International
License: Creative Commons Attribution Share Alike 4.0 International
Great work!
Just a micro remark: Wouldn't it be better to remove the arrow in the Customer-Supplier picture or turn it around?!
I mean the "Customer gets" something which the "Supplier provides". Or did I miss something?
Best greetings
Stefan
How big is a domain? How big is a bounded-context?
Does a bounded-context belong to a (only one) team (squad in Spotify Model)? Can a domain small-sized to belong to a team? Or does it always represent a bigger thing (like an entire company and its business units* - or each business unit is a domain...)?
I am deep-diving in the DDD's world and I would like to hear some opinions about hierarchies (agg root, bounded context, domain, [after domain?]) and the right size (if that is possible).
*business unit in this context is a line of bussines attended by the company. Example: a bank (company) can offer stock services, core banking services or loans - each as a independent line of business.
Thanks
Could someone please explain better why the "Partnership" and "Customer-Supplier" are patterns and not team relationships? It seems like a mistake of categorization.
Even the explanation of these "patterns" begin with teams relationships.
If the aim of the repo is to simplify the understanding, I think it would be greate to either fix the categorization issue or explain why it was made this way.
I think Evanse's book is not a Bible and could tolerate new interpretations, doesn't it?
Hello,
In the second example, the text is "C and D are mutually dependent" while it's C and B.
HTH.
Hello, can I have access to post a PR, on this repo?
First thanks for your work.
Do you think the interchange context pattern as described by Eric Evans here could be a candidate ?
The page:
https://virtualddd.com/learning-ddd/ddd-crew-context-mapping#contributions-and-feedback
has a broken link to:
That should probably be:
Hello @mploed
I was wondering if you had already seen or done such a thing: having a 2 levels context maps where 1st level would focus only on team relationships and 2nd level, only on context map patterns.
Here's an example:
(and yes, obviously the Cus-->Sup relationship should be the other way round ;) )
What do you think? Does it make sense or useful to separate both perspective?
Thanks!
Maxime
A declarative, efficient, and flexible JavaScript library for building user interfaces.
๐ Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
An Open Source Machine Learning Framework for Everyone
The Web framework for perfectionists with deadlines.
A PHP framework for web artisans
Bring data to life with SVG, Canvas and HTML. ๐๐๐
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
Some thing interesting about web. New door for the world.
A server is a program made to process requests and deliver data to clients.
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
Some thing interesting about visualization, use data art
Some thing interesting about game, make everyone happy.
We are working to build community through open source technology. NB: members must have two-factor auth.
Open source projects and samples from Microsoft.
Google โค๏ธ Open Source for everyone.
Alibaba Open Source for everyone
Data-Driven Documents codes.
China tencent open source team.