A county clerk wants building permits, fees, and inspections as separately deployable services, each with its own data store, so one team's release does not freeze the others. Which pattern matches that goal?
Select an answer to reveal the explanation.
Short Explanation
Think of three shops on Main Street with their own keys and cash drawers instead of one locked front door for everyone. Separate services with their own data stores let permits ship without freezing fees or inspections. That is microservices with bounded contexts.
Full Explanation
Microservices isolate deployable units around bounded contexts so teams release independently and avoid a single shared schema bottleneck. A monolith or shared-database multi-module app still couples releases. A warehouse ETL is analytics, not the online transactional path. Separate data stores plus independent deployability are the hallmarks that match the clerk's requirement.