Dedicated Container

Dedicated Storage Container

For complex or heavily loaded applications, shared data can be centralized in a dedicated storage container. This provides simpler and more flexible management of exported data, including separate read-only and read-write access permissions for different node types.

Within the platform, a Shared Storage Container is recommended when files must be shared across several application layers, environments, or both. It is optimized for data storage, with an emphasis on performance and increased disk capacity.

On this page

Storage Container Overview

A dedicated Shared Storage Container acts as an independent storage node. Applications and environments can mount the required folders and use the same data without storing duplicate copies on each application server.

Benefits of a Separate Shared Storage Container

Independent resource handling

Because storage is maintained in an independent container, temporary storage load can be handled separately without reducing overall application performance.

Simpler project recovery

Application nodes can be removed and recreated while the required storage data remains available. Common environment settings, including internal domains and sharing permissions, can remain unchanged and simplify reintegration.

Better lifecycle separation

Keeping data in a separate container makes it easier to manage cloned environments for development, testing, staging, and production.

Safer database backups

Folders containing scheduled database backups can be mounted to the storage container so backup files are stored remotely from the database or application node.

Best Practice: Keep persistent files and backup data outside disposable application nodes whenever your architecture allows it.

Sharing Common Configuration Files

In addition to storing application data, the same architecture can be used to share common configuration files between nodes located in different layers or environments.

For example, several application servers can mount a shared configuration directory so that each node reads the same centrally maintained files.

Note: Define appropriate access permissions for every mounted folder. Some nodes may require read-only access, while trusted application nodes may require read-write access.

Using the Container as External Storage

A Shared Storage Container can also operate as external storage. Data stored on the platform can be exported and made accessible through the Internet.

This approach can be used to share selected content with a third-party service, another developer, or another platform installation. Individual access permissions can be assigned according to the required level of access.

It can also be used to create an intercloud data-sharing setup in which several PaaS installations access the same data through a platform-hosted NFS server.

Security Note: When exposing storage externally, restrict access to trusted systems and users. Review network rules, NFS permissions, and read-write privileges before publishing the storage endpoint.

Learn How To

Operate a Shared Storage Container

Create and manage a dedicated storage node for application data.

Add Mount Points

Mount remote folders to application containers and environments.

Export Data Between Nodes

Make data from one container available to another container.

Configure External NFS Storage

Configure a container as an external NFS server.

Connect External NFS Storage

Connect a remote NFS storage server to a platform environment.

Expected Result

  • Shared application data is stored independently from application server nodes.
  • Multiple containers or environments can access common files through mounted folders.
  • Storage load can be managed separately from application processing.
  • Persistent files remain available when application environments are rebuilt or cloned.
  • Selected data can be shared with external systems through NFS-based access.