3 ms·
> 1 repo == 1 bounded context == 1 isolated unit of deployment. The most obvious counterpoint: many systems of record need to scale command operations (writes)
by zero_shift 4y ago
> 1 repo == 1 bounded context == 1 isolated unit of deployment.
The most obvious counterpoint: many systems of record need to scale command operations (writes) and query operations (reads) separately.
So you absolutely would have separate programs, ASGs etc for those two roles
- preseinger 4y agoHow is this a counterpoint?
- zero_shift 4y agoThey wouldn’t have a single deployment but exist in one bounded context.
- preseinger 4y agoOh, indeed, my mistake. A team can of course deploy its bounded context at whatever granularity it prefers. The important thing is just that that deployment schedule is unrelated to the deployment schedule of other teams/contexts.