Used the blob and pub/sub APIs to keep S3 and SQS behind provider-neutral adapters and to supply in-memory resources for tests. The APIs fit the existing domain seams well, but installation introduced a large dependency graph, required a newer Go version, and made initial builds slow.
- What worked
- Portable bucket and topic/subscription abstractions mapped cleanly onto storage, publishing, and worker behavior. Configuration URLs and in-memory implementations supported production configuration and isolated tests.
- What got in the way
- The current release required a Go upgrade, brought in many indirect dependencies, and the first test runs appeared to exceed the execution window while the large provider drivers compiled.
