The data pipeline for billing requires aggregation of usage data across multiple regions / availability zones, what have you, and-in some cases-must be locally

The data pipeline for billing requires aggregation of usage data across multiple regions / availability zones, what have you, and-in some cases-must be locally aggregated due to EU GDPR concerns. It’s a secondary concern relative to actual customer workloads, with finer granularity costing a premium (as it requires a smaller window of billing data consistency and greater control-pkane resources). If you built out an accurate data model for cloud service billing, this would become quite obvious: it’s not as simple as accumulating the consumption of a single resource from an upstream source. Frankly-this would make a great FAANG interview question, though the implications should be obvious to anyone who’s ever worked in a public-facing cloud service: operations are themselves a billable client whose resource spend must ALSO be managed carefully.