A DMV modernization program proposes services named “all database access,” “all UI widgets,” and “all batch jobs.” Which boundary approach better supports independent business change?
Select an answer to reveal the explanation.
Short Explanation
Useful cuts follow the business—like a “checkout” counter that owns its flow—not a basement of “all database access.” Capability-oriented boundaries let a team ship end-to-end. Layer-shaped slices force lockstep releases when a change crosses the stack.
Full Explanation
Microservice boundaries work best when aligned to business capabilities owned end-to-end. Horizontal technical layers still require coordinated releases whenever a business change spans UI, data, and jobs. Collapsing everything into one platform-core or organizing solely by language team does not create capability ownership.