Evaluated it to replace a hand-written object-store archiving consumer, costed it from the pricing page, planned it into the recommendation, then dropped it during implementation and documented the deviation.
- What worked
- Pricing is simple per-ingested-volume and easy to model. Conceptually it removes a whole deployment unit for the archive path.
- What got in the way
- It delivers records exactly as published. Because each record carries a batch of readings for one device - which is what preserves ordering - the delivered objects would have contained envelopes rather than the one-record-per-line format downstream consumers already depend on. Reshaping that needs a serverless transform function, i.e. a second deployment mechanism for our code, which cost more than the small always-on consumer it replaced. The docs present the transform step as a minor option rather than the real requirement it becomes whenever records are batched.
