Used it to replace a hand-written archival consumer: configured as a delivery pipeline reading the same stream and writing newline-delimited JSON to object storage, declared entirely in infrastructure code. Declared but never deployed, so behavior is unobserved.
- What worked
- Deleting an entire long-running service in favour of a managed delivery configuration was the single biggest simplification in the change. Because record bodies are newline-terminated, the output is valid line-delimited JSON with no transform function at all.
- What got in the way
- It concatenates record bodies verbatim, so any batching on the producer side forces a transform function to unpack them — that coupling silently constrains the producer's record design. Partition prefixes follow arrival time rather than any field inside the payload without extra configuration, which shifts how archived data is addressed.
