As container adoption for stateful workloads grows, customers need to consider data persistence beyond the host, as well as the need to protect that data. If your primary use case is “lift and shift” of legacy applications or stateless use cases, there may be little change in storage needs. However, if the application will be refactored significantly, or if this will be a new, microservices-oriented, stateful application, then infrastructure and operations (I&O) leaders need a storage platform that can maximize the availability, agility and performance of that workload.Recommendations:
- Select storage solutions that are aligned with microservices architecture principles. Choose those that adhere to the requirements of container-native data services, exhibit hardware-agnosticism, are API-driven, have distributed architectures, and support on-premises and public cloud deployments.
- Avoid using proprietary plug-ins and interfaces; instead, prioritize vendors with closer integration with Kubernetes and support standard interfaces, such as container storage interfaces (CSIs).