@SzymonPobiega In my view, a service can be composed of/implement/host one or more bounded context. No BC is hosted by more than one service
1
@SzymonPobiega Unless it's something entirely technical/cross cutting, I'm a strong advocate of avoiding shared code wherever possible
2
@stilkov When I mentioned splitting BC I meant different code sitting in each service. Only the language would be same/shared.
1
@SzymonPobiega Might be I'm not up to the full DDD terminology, but I thought a bounded context can't be split? //cc @VaughnVernon
1
@stilkov @VaughnVernon Sorry, another shorcut. I meant there are 2 services, each implementing different model but both models share context
1
@SzymonPobiega @vaughnvernon That was my understanding, yes. I advocate against sharing code, even in that scenario :-)
1
@stilkov @vaughnvernon Share language, not code. Or from the other perspective, split implementation. I am not advocating,only acknowledging
1
@SzymonPobiega @vaughnvernon Interesting, so you'd qualify some parts of the code as language and another as implementation?
Jan 25, 2013 · 9:59 AM UTC
1