Databases
Managed database overview
LiveHow StackShift databases fit into the platform and how they differ from stack-hosted stateful services.
Goal
Understand the managed database model before creating or restoring one.
Current status
Live
This area is documented as current, user-reliable behavior.
Workflow
- 1Treat databases as their own resource type, not as special cases of stacks.
- 2Use database views for connection info, backups, and restore flows.
- 3Expect current backup behavior to be S3-backed, not the older AWS/EBS model described in stale docs.
What the database surface includes
- Provisioning and health state separate from stacks
- Dedicated credentials and connection details
- Dedicated backup and restore workflows
How this differs from a database inside a stack
A managed database is tracked as its own platform resource. A database container inside a stack is still part of that stack. The operational surfaces, backup flows, and recovery expectations are different, so it is worth choosing deliberately instead of treating them as interchangeable.
Expected result
You can reason about StackShift databases as a separate platform surface.