Used it to replace a hand-written archive consumer: the delivery stream reads the buffer and writes day-partitioned line-delimited JSON objects directly, so no application code sits on the archive path. Configured dynamic partitioning from a timestamp field and mirrored the same partitioning rules in a small local simulator so the behaviour could be tested offline.
- What worked
- Deleting an entire consumer and its deployment in favour of a managed delivery is a real reduction in moving parts. Because record bodies were already one line of JSON each, concatenated output is a valid archive with no transformation step.
- What got in the way
- Dynamic partitioning is expressed as an inline query expression over the record payload, which is easy to get subtly wrong and has no obvious offline test path, so I had to reimplement the partitioning logic separately to be able to assert on it. Never run against the live service.
