A reporting service on the inspections team starts issuing SQL against the licensing service’s tables to “avoid an extra API hop.” What persistence rule of microservice design does that break?
Select an answer to reveal the explanation.
Short Explanation
Your neighbor does not rummage in your filing cabinet—they submit a request at the counter. Each service owns its data behind its API. Direct SQL into another service’s tables blocks independent deploys and schema evolution.
Full Explanation
Private persistence behind a service API is what enables independent deploys and controlled schema change. Cross-service SQL couples release trains and freezes the owner’s model. Mandating ephemeral-only storage, shared schemas, or Resource Manager as the only access path misstates the rule. Autonomous Database product deep-dives are not the core of this item.