1 Shared dependencies
Run one Redis cluster, one Postgres cluster, and one S3-compatible blobstore across the suite. Every service supports namespaced prefixes so they can share Redis without collision.
2 Authentication
Set SHARED_WS_KEY once and let every service inherit it. Or use an OAuth provider — Parachute, Dockyard, and Slipstream speak OIDC.
3 Networking
Put services behind an ingress with a consistent subdomain scheme (flytrap.int, stash.int, etc.). Each service is self-contained behind its own host.
4 Backups
Backup Postgres and your S3 buckets. Redis is usually ephemeral queue state.
5 Scaling
Stateless services scale horizontally. Workers for media services scale by replica count. Tune QUEUE_WORKERS and STORAGE_CONCURRENCY per service.