x-new-adapter

A Go adapter package requires defining its position in the package tree and establishing a public contract. This scaffolding approach ensures integrations for storage, queues, or databases remain reproducible and testable.

Configuring a Go infrastructure adapter requires building Config via an environment workflow. Constructors must remain free of I/O operations to maintain a clean lifecycle and ensure the adapter is easily testable.

Wiring observability into a Go adapter package is a core scaffolding decision guided by the adapter's lifecycle. It connects the public contract to observability practices, ensuring external system integrations are properly monitored.

Selecting unit and integration tests is a key step in adapter creation. The strategy involves choosing appropriate tests to validate the public contract and ensure the infrastructure adapter behaves correctly with external systems.

Your Go adapter should use the external library's types as the real public contract. This approach prevents duplication and clearly defines the contract for both the adapter and its consumers.

You need an adapter package when integrating external systems like queues, storage, databases, or executors. It eliminates architectural chaos by defining a clear public contract, lifecycle, and observability wiring.