Data Synchronization

Workaround of the Data Synchronization

When several PHP application-server instances are required, the additional nodes can receive an initial copy of the project data from the first node during horizontal scaling.

The workflow below creates a single application-server node, deploys and configures the application on that node, and then scales the layer horizontally so the newly added instances are created with the initial project data.

On this page

Create the Environment

1Open the platform dashboard

Sign in to the platform and click Create environment or New Environment.

2Configure the initial topology

In the topology wizard, select one PHP application-server instance and add any other required services. Enter the environment name and click Create.

Create a PHP environment with one application server
Start with one PHP application-server node before deploying and configuring the project.

Upload the Application

3Open Deployment Manager

Upload the application package from a local file or provide an archive URL.

Upload application archive
Upload the project archive through Deployment Manager.

Deploy and Configure the Project

4Deploy the uploaded package

Select the archive in Deployment Manager, click Deploy to, and choose the target environment.

Specify the application target path when several projects need to be hosted on the same server, then click Deploy.

Deploy application to the selected environment
Choose the target environment and optional application context.

5Complete the initial configuration

Wait for deployment to finish and make all required application and server configuration changes while the layer still contains a single node.

Scale the Application Layer

6Add the required server instances

Open the topology wizard for the existing environment and increase the number of PHP application-server nodes.

The newly added instances are created using the initial node as the source, so the deployed project and the configuration available at that moment are copied to the new containers.

Data synchronization during horizontal scaling
Increase the node count after the project has been deployed and configured on the initial server.
Initial Data Copy Project files and existing configuration are copied when the new nodes are created.
Horizontal Capacity The additional PHP nodes can then share application traffic through the configured load-balancing layer.

Synchronization Limitations and Alternatives

Initial synchronization only: Changes made after horizontal scaling are not automatically synchronized between the application-server nodes.
  • Use the file manager when deploying the application to achieve the initial synchronization effect described above.
  • Later file or configuration changes are not replicated automatically.
  • For an existing multi-node environment, scale the layer down to one node, apply the required data or configuration changes, and then scale it up again.
  • Use WebDAV where appropriate to synchronize or manage shared files.
  • Use the Configuration File Manager for manual configuration updates.
  • The initial master node can be used as a storage server to share data across the layer.
For continuous file consistency across application nodes, use a shared-storage or dedicated file-synchronization solution rather than relying only on the initial scaling copy.

What’s next?