I was referring to the context, it is very early where I am :). I agree with you, I have never built a microservice > 4 services. The business never modeled itself that way. I can't imagine trying to manage or do change control on 20+, crazy.
1
Hey, Heath! I am in Arizona so on the same wall clock as you. Thanks for your comments. I didn't mean to step on your toes. This whole bbom-monolith-micro-now-macro thing has and will cause so many problems. Someone at BigCo launches a new really bad name and everyone jumps.
3
2
There is an existing name/pattern that describes this fairly well: Self-Contained Systems. I have issues with the name and a few definitions, but it is definitely a great place to start. /cc @stilkov @bitboss
- "System" - too broad
- "core domain" - nope
scs-architecture.org/
3
4
13
Briefly
- System (also) has too many meanings. I've concluded that N deployed independent Bounded Contexts are together a System. However, I am pretty sure that Donella H. Meadows would agree that an SCS is indeed a System.
1
1
2
- In the SCS infodeck is a statement that within a SCS there are potentially multiple domains and a core domain. I assume it means "models." Although this ok with DDD, I think that it is spelled "Core Domain" and means differentiating value. I think of Core Domain == SCS.
2
2
In other words, a Core Domain is not just the most important model in any ol' Bounded Context.
Also we should strive for 1:1 model and Bounded Context.
For example, a Supporting Subdomain could possibly have that situation, but it is definitely not a DDD "Core Domain."
1
2
This is, of course, in terms of DDD. Perhaps you didn't have DDD precisely in mind when you codified SCS. So it's understandable that you could have the case of multiple models and the most important model in one SCS.
2
1
From my limited understanding, the core domain (in DDD terms) could be spread across multiple SCSs, but doesn’t have to be
Apr 12, 2020 · 2:59 PM UTC
1
1