backend

Overview ¶

Package backend is the seam between the local provider and what actually serves a resource in a development session.

The provider knows which resource kinds a session has to serve itself and which it hands to the platform's provider. What serves them is a separate decision: today a queue and a topic are Redis, because that is what the runtime's consumer side reads locally, and nothing about the provider assumes it. A backend package registers what it can build when it is linked, and the provider asks here rather than importing it.

The same arrangement as the AWS module's internal/service, for the same two reasons: a session whose blueprint declares no queue does not link a Redis client for one, and a backend that is not Redis can be added without the provider learning about it.