Section Introduces Persistent Volume Storage Support for Distributed Multi-Cloud Kubernetes Workloads

Section announced support for Persistent Volume storage across its distributed, multi-cloud platform, allowing developers to quickly deploy even the most complex Kubernetes workloads globally. Section enables organizations to easily optimize and scale service to local demand while steering traffic to the most appropriate endpoints for performance and availability across cloud providers worldwide. With the new release of Persistent Volumes, Kubernetes users can ensure stateful data storage independent of pods and containers to support Databases such as PostgreSQL and MySQL, shared caches, document or object stores and more. Section handles day-to-day server operations, as its clusterless platform automates orchestration across a secure and reliable global infrastructure network.

“Effectively orchestrating distributed applications and storage is devilishly complex,” said Stewart McGrath, Section’s CEO. “But not with Section. We’re giving organizations simple access to a global platform so they can quickly deploy and scale – even for complex environments that require Persistent Volumes – freeing up valuable development time and resources.”

Developers deploy on Section’s multi-cloud, clusterless platform using Section’s web-based console or standard open-source tools (like Helm, YAML or kubectl), setting simple policy-based rules to automate global orchestration. While typical workloads can readily use ephemeral storage as needed, Persistent Volumes can now be created dynamically through a Persistent Volume Claim.

“Persistent Storage has been something customers have been talking to us about,” said Dan Bartholomew, Section’s chief technology officer. “This feature opens up a whole range of new applications to run on Section and is something we’ve been able to support through all of our infrastructure partners from day one.”

Persistent storage on Section can be used for:

• horizontal scaling of a pod, so that the multiple replicas have access to common data, such as a cache
• different pods of a microservice application, giving those pods a common source of truth for whatever data they might need
• data that needs to survive a pod that crashes and restarts
• a database for your distributed application, such as Postgres, MySQL, SQLite, or others
• a document store
• a persistent cache, for use with technologies such as Varnish
• a KV (Key Value) store
• an object store, such as MinIO

Once applications are deployed on Section, users will experience an instant performance boost from reduced latency, while application availability and resilience are dramatically improved by Section’s automated service failure/re-routing capabilities. Organizations will benefit from decreased costs versus hyperscalers or roll-your-own distribution solutions. Section’s distributed cloud-native compute platform allows application developers to focus on business logic while enabling their software to behave as if it runs everywhere, is infinitely scalable, always available, maximally performant, completely compliant, and efficient with compute resources and cost.