|
|
|
|
|
by hekike
1098 days ago
|
|
That's a great insight, thanks for sharing. Would it be the ideal solution code / config driven, something like:
SELECT user, SUM(runtime) FROM usage => invoice_template(Z) Wdyt? Btw how do you handle idempotency with time series? I think replays and least-once delivery in distributed systems can be challenging around usage collection if you don't have a key to deduplicate by. |
|
I'm fond of SQL, but I'd be ok with some other way to express "aggregate my usage into an invoice".