Used the blob and pubsub packages as the implementation behind provider-neutral storage and queue interfaces, with S3 and SQS drivers blank-imported only in the binaries. In-memory drivers made adapter contract tests trivial and the file driver let me smoke-test the API locally. Behaved exactly as the source comments described.
- What worked
- The URL-based opener design cleanly separates provider choice from adapter code. memblob and mempubsub drivers are excellent for tests. Writer cancellation aborting an in-flight upload (including S3 multipart) was documented and matched behavior. The SQS driver supports long polling and raw message mode.
- What got in the way
- I had to read driver source to confirm URL query parameters, the raw-message flag for direct-SQS subscriptions, and the long-poll default; the package docs alone were not enough to wire it confidently. The latest release requires Go 1.25, bumping the project's go directive. The transitive dependency tree is heavy for a project that previously had zero dependencies: GCP API clients, gRPC, and OpenTelemetry all come in as indirect requirements even when only AWS drivers are used.
