An integration caches full UCS and Intersight compute inventory documents that differ by product family and are almost always read as whole objects after each API revision. Which store type is the best fit?
Select an answer to reveal the explanation.
Short Explanation
Variable-shaped API payloads are like differently packed moving boxes—you usually want the whole box, not a fixed drawer layout. Document stores embrace that flexibility. Forcing a brittle relational schema for every UCS/Intersight revision is the mismatch.
Full Explanation
When records mirror heterogeneous platform JSON and are retrieved as whole documents, a document store matches the access pattern. Relational rigidity fights frequent API shape changes; columnar and time-series layouts target analytic scans and timestamped measurements, not whole inventory objects.