One Bounded Context Per Service (mostly)

Why service boundaries should follow context boundaries.

0/1 done

Theory

The default — and almost always right — answer is: one service per bounded context. The context already represents a model that's consistent inside and translated at the edges; that's exactly what a service should be.

Splitting below the context level produces distributed monoliths. Splitting above it produces shared databases.

Reading in progress · 0 of 1 activity done