Forking Deployments

There are situations in which you might want to duplicate an existing Deployment including its application state at a well-defined point in time. For example, you might want to

  • reprocess the stream of events since an application upgrade with a patched version of your application
  • run a new version of a recommendation algorithm side-by-side with your running application (e.g. for A/B testing)

In Ververica Platform this operation is called “forking” a Deployment. When you click on “Fork” on the Deployment Overview Page a new Deployment named “Fork of <name>” is created in “CANCELLED” state. No State is carried over to the new Deployment.

To start your forked Deployment from a state snapshot, you can select “Fork Deployment from Snapshot” from the “Actions” drop down of each snapshot in the “Snapshots” Tab of the original Deployment. In that case, a reference to this Savepoint (with origin “COPIED”) will be added to the newly created Deployment, which will be considered by its RestoreStrategy once started.

Forking is only available in the web user interface (Deployment Overview & Snapshots Tab). If you want to fork a Deployment via the REST API, you can do so by executing the steps above one by one via the REST API.