为什么按使用量计费必须被视为基础设施（由 Metronome 赞助）.pdf

《为什么按使用量计费必须被视为基础设施（由 Metronome 赞助）.pdf》由会员分享，可在线阅读，更多相关《为什么按使用量计费必须被视为基础设施（由 Metronome 赞助）.pdf（24页珍藏版）》请在三个皮匠报告上搜索。

1、 2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.2025,Amazon Web Services,Inc.or its affiliates.All rights reserved.Austin WortleySolutions EngineerMetronomeWhy Usage-Based Billing Must Be Treated as InfrastructureA I M 1 0 9-SWhy Usage-Based Billing Must Be Treated as Infrastruct

2、urere:InventIntroductionAustin WortleySolutions EngineerMetronomeMetronome powers monetization infra for the most innovative companiesEmbracing theThird WaveMonetization is now real-timeBilling(how we traditionally think about it)Monetization(how companies need to think about it)Real-timeCore produc

3、t experienceIn-the-moment workflowsStrategic growth leverBatched process Monthly invoices Backward-looking Finance operationDetached from productMonetization is an infrastructure problemAny event that impacts revenueAPI call madeInference executedServer spun up or downResource heartbeat“Business eve

4、nts”Invoices,credit burndown,real-time spend threshold and fraud notifications,raw revenue data“Invoices&Revenue Data”Why is this hard?CorrectnessHigh availabilityTransactionalobservabilityPick twoLow latencyWhy is this hard?It is financial truthBilling,compliance,revopsCorrectnessLow latencyHigh av

5、ailabilityEvents may arrive out of orderWhy is this hard?Alerts for entitlement gating and fraud detectionCorrectnessLow latencyHigh availabilityYour customers expect dashboards to be updated now,not in hours/daysWhy is this hard?APIs power customer provisioningCorrectnessLow latencyHigh availabilit

6、yData export powers C-suit dashboardsEven when your product goes down,billing cantWhy is this hard?CorrectnessHigh availabilityTransactionalobservabilityPick twothreeLow latencyScalabilityModularityOrchestrationExtensibilityInfrastructure principles applied to monetizationScalabilityHandles real-tim