January 2018
Beginner to intermediate
312 pages
7h 22m
English
Let’s start with the concept of a “bounded context” and how it relates to an architecture. As we saw earlier, it’s important that a context is an autonomous subsystem with a well-defined boundary. Even with those constraints, though, we have a number of common architectural styles to choose from.
If the entire system is implemented as a single monolithic deployable (a single container using the C4 terminology above), a bounded context could be as simple as a separate module with a well-defined interface, or preferably, a more distinct component such as a .NET assembly. Alternatively, each bounded context could be deployed separately in its own container—a classic service-oriented architecture. ...
Read now
Unlock full access