Monetizing Your Applications Using Cloud Foundry Abacus and Billing Engines
summary
CF Abacus runs as six microservices to meter API usage (meter → collect → accumulate) and persists records (demo uses pouch server; production uses MongoDB). The demo sends three usage events (10 reserved calls, 300 pricing queries, 300 imagery calls), pushes them to Revenue Cloud, which maps them to a subscription product space trip basic with a $5 signup fee, 10 included calls and per‑call rates, and produces one consolidated invoice applying included allowances and billing excess usage.
AI-written summary · about
chapters (13)
- 0:00Introduction and session overview
- 1:54Sci-fi API monetization setup
- 4:01Ecosystem actors and compensation
- 5:25CF Abacus metering engine explained
- 7:55Billing engines and revenue cloud
- 10:03Billing architecture and quote-to-cash
- 13:13Demo setup and CF Abacus run
- 18:17Revenue cloud product configuration
- 21:10Usage aggregation and billing
- 24:30CF Abacus capabilities and alternatives
- 25:33Complex ecosystem and future plans
- 26:50Internal chargeback models
- 28:44Conclusion and key takeaways
related talks
25mMonetizing Your Applications Using Cloud Foundry Abacus and Billing Engines - Pankaj Kumar, SAP
30mDesigning an Extensible Billing Platform using Domain-driven Design
54mScaling Web Services for Free to Play
47mManaging Application Events in the Cloud
24mCloud Foundry Cookbook
31mCloud Foundry and Microservices: A Mutualistic Symbiotic Relationship
34mCloud Chaos and Microservices Mayhem
22mOperationalising Data Science on Cloud Foundry