For platform and infra teams
Check what depends on a database before you migrate it
A database appears in diagrams across the workspace. Open its Dependencies tab to see the direct and indirect dependents recorded in those diagrams before you plan the move.
Sound familiar?
- Which services still read from the old database? I need a list before we move it.
- The infra diagram in the wiki predates the last reorg.
- Each team has a copy of the network diagram, and they disagree.
Reuse the same infrastructure objects
Keep a catalog of the services and databases in your architecture. Reference an existing object when you add it to a diagram so another team can find the same definition.
Draw from imported resources
Cloud import (Beta) brings supported AWS, Azure, Google Cloud and Kubernetes resources into the catalog. Generate a diagram from imported resources, with infrastructure boundaries around them.
Keep diagram changes in code review
A diagram has YAML source you can edit beside the canvas. Keep it next to your infrastructure code in Git and review the changes in the same pull request.
A migration plan, start to finish
Open the database object and check its documented dependents.
Draw the target deployment in a new document.
Link the migration decision to the database object.
Share the plan with the engineers responsible for those dependents.
AWS deployment architecture
Place an API cluster and PostgreSQL databases inside account, VPC and subnet boundaries.