Microservices Patterns — Series 2

Preview — 3 of 10 questions

A legacy checkout is replaced incrementally. What makes a strangler migration controllable?

AKeep two unrelated authoritative implementations accepting all writes.

BMove every table first and rewrite all callers in one release.

CExtract one routed capability with a fallback path.

DDelete legacy routes before the replacement has production validation.

Two services share a database cluster but have separate schemas and credentials. What determines whether ownership is respected?

AEvery service must run on a physically separate database machine.

BSchema naming alone prevents all cross-service coupling.

COnly the owning service can change or expose its internal data contract.

DAny service may query another schema if the query is read-only.

Mobile needs a compact dashboard; web needs a richer aggregation. What is a reasonable BFF boundary?

AOne BFF database becoming the writable source for every domain.

BA full independent implementation of payment rules in each BFF.

CA separate backend deployment for every individual UI component.

DClient-specific composition; shared domain rules stay in services.

Answer all 10 questions (7 more), see explanations for every answer, and track your score.