Charging for what customers actually consume

Apache Camel and RabbitMQ connecting a private cloud provider’s billing system to its infrastructure management tooling.

Talk to an engineer ServiceNow

Private cloud Client

ServiceNow Practice

July 2023 Published

01 — The challenge

Where it started.

The provider needed to bill on actual consumption — CPU, memory, storage and bandwidth — and the systems holding that consumption data were not the systems producing invoices.

Without a dependable link between the two, revenue is estimated rather than measured.

02 — What we built

The work itself.

Apache Camel between billing and infrastructure. Routes connecting the billing system to the cloud management tooling, with transformation handled in the integration layer rather than inside either system.

RabbitMQ carrying the metering. A message queue sized for the volume of metering events, so accuracy does not degrade under load.

03 — Results

What the client has now.

Customers billed accurately on real resource utilisation. Revenue streams optimised against measured consumption. Customer satisfaction improved by billing that matches usage.

The rest of this study

What we built, what it produced, and the stack behind it.

We share the whole write-up — we would just like to know who is reading. One form opens every case study on the site for the next 30 days.

If this is your problem too

Start with a fixed-price pilot.

Two weeks on a real piece of your backlog, priced before we begin. You keep the output whether or not you continue.

Related work

Private cloud · ServiceNow ITSM

Untangling a complex IT environment

Healthcare · Systems integration