Migrating Incrementally

How to shift from your existing environment to Facets Managed environments incrementally

Overview

The aim of this document is to guide the user on performing incremental migration to Facets from their existing architecture.

Introduction

Lift-and-Shift is never desirable, whether you are experimenting with Facets Control Plane or switching from your current setup to Facets.

Steps to Migrate

In this Section, you will learn how to incrementally migrate to Facets-managed environments.

582

Co-existing environments

The illustration above shows a common software architecture configuration. The left side of the setup would already be complete, with your internal platform powering the environments—in this case, three environments: QA, Stage, and Production.

  1. Set up the Facets Control Plane. Refer to the Set Up your Control Plane document to learn more about it.
  2. As shown in the Create your first Blueprint document, initiate an empty Git repository.
  3. Commit stack.json, features.json in this repository.
  4. Create three empty environments. Refer to the Launch an Environment document to learn about creating an Environment.

    📘

    Note

    These new environments can be in different cloud provider accounts as well.

  5. Peer your existing environments with the newly created environments in Facets. Refer to the Peering guide to learn more about how to establish bi-directional communication between your environments and environments provisioned in Facets.
  6. Pick one of the services from your application, add it to the Blueprint, and deploy it to Facets-managed environments. Refer to the Performing a Release document to learn about deploying an environment in Facets.

You have successfully migrated the service to the Facets Control Plane.