BackingServicesAttached [principle] v1.0.0

Treat databases, caches, message queues, SMTP servers, and other backing services as attached resources accessed by URL. The app code makes no distinction between a local Postgres and a managed RDS — they are both just a connection string. Resources can be swapped without code changes.

Backing services are URLs in env, not addresses in code. The app does not know if its database is on the same host or across the planet.

Applies To

• DB connection: read DATABASE_URL from env, not hostname-port-user-pass constants.
• Switching local SQLite to managed Postgres for production = config change, not code change.
• Detaching a misbehaving cache replica and pointing at a fresh one is a deploy, not a hotfix.

BackingServicesAttached [principle] v1.0.0

Treat databases, caches, message queues, SMTP servers, and other backing services as attached resources accessed by URL. The app code makes no distinction between a local Postgres and a managed RDS — they are both just a connection string. Resources can be swapped without code changes.

Backing services are URLs in env, not addresses in code. The app does not know if its database is on the same host or across the planet.

Applies To

• DB connection: read DATABASE_URL from env, not hostname-port-user-pass constants.
• Switching local SQLite to managed Postgres for production = config change, not code change.
• Detaching a misbehaving cache replica and pointing at a fresh one is a deploy, not a hotfix.

Relations

requires: [@backend-architecture/principle-config-in-environment]

Requires

• @backend-architecture/principle-config-in-environment