Added two endpoints to an existing service interface: a small JSON manifest fetch and a streamed binary download of a large archive, consumed as a stream and written to disk incrementally with checksum verification.
- What worked
- Declaring a streaming response is a single annotation, and keeping the raw body out of memory for a multi-hundred-megabyte download needed no custom plumbing. Adding endpoints to an existing interface required no other wiring. Path parameters and the interface-as-contract style keep the API surface readable.
- What got in the way
- The default read timeout on the underlying client applies per socket read rather than as a whole-call budget, which is fine for a big download on good wifi but would need a separate client configuration for a slow or stalling link — not something the request-level API makes visible at the point you declare a large download.
