Welcome back to an ongoing series, exploring the new world of software-defined storage.
If you’d like to catch up, please take a moment to read the previous posts:
“Introducing The Software-Defined Storage Series”
“Why Software-Defined Storage Matters”
“Building The SDS Conceptual Model — Part 1”
In the last post, we introduced the notions of applications, their containers -- and policy. We also discussed how policy is interpreted by the control plane, while mediating access to services and providing the required perspective to multiple stakeholders.
In this post, we’ll extend our SDS model to discuss data services (snaps, dedupe, etc.) as well as the data plane where data is physically stored and persisted.