A project team debates whether citizen records need rigid relational schemas or flexible documents, while another debate asks who patches the database engine. What distinction should the architect emphasize?
Select an answer to reveal the explanation.
Short Explanation
One argument is about the shape of the data — tables versus documents. The other is about who changes the oil on the engine — you or the provider. Do not mash them together: you can run relational or document models either self-managed or managed. Keep those two dials separate.
Full Explanation
Cloud database decisions include at least two orthogonal axes: the data model (relational versus non-relational/document and related patterns) and the operational model (self-managed versus provider-managed). Conflating them leads to poor requirements mapping. Hypervisor brand, object-only assumptions, and tagging do not resolve either axis.