Here is how the resource-based pricing would work in practice
To explain our resource-based pricing calculation, we will present a typical scenario of an e-commerce online shop and ERP / CRM integration solution adopted from one of our use cases. These calculations are here for your guidance only. For exact calculations and estimates please contact our sales.
Acme e-commerce integration
Product sync - synchronises product data from Product Information Management system (PIM) into an e-commerce storefront. It is scheduled to run every night at 03:00am. There are 5000 products synchronised every night.
Customer and Order synch - two integration flows that are running every 5 minutes and poll data from e-commerce storefront to internal ERP and CRM systems. There are 200 orders completed in the storefront per day.
Shipment notification - is an integration flow that is triggered by a Webhook from a logistics service provider that updates the shipment status inside internal ERP and CRM systems. We assume it's triggered 4 times per each order.
Availability check - is a realtime type integration flow providing a stock check for selected products with sub-second response time. Executed once per order - before order completion.
|Task name||Single run-time||Number of execution
for single run
|Used monthly resources
|Product sync||10 min||31||1280 MB||6|
|Customer sync||30 sec||8928||512 MB||37|
|Order sync||30 sec||8928||512 MB||37|
|Shipment notification||20 sec||12400||512 MB||31|
|Availability check||n/a||n/a||384 MB||279|
When executed every 5 minutes, it would make 12 executions per hour. Calculated 24 hours per day and 31 days per month = 12 x 24 x 31 = 8928 times per month.
Realtime integration flows are constantly up and running to achieve sub-second response time. Therefore, memory is consumed 24 hours per day. Calculating for 31 days makes 744 hours per month.
For your guidance 1GB = 10,000 Data records on average.