Interesting that we aren't discussing a tiered off the shelf solution.
We were discussing the processes of mapping incoming events by
classification into some table of tariffs, applying any found cost, then
aggregating such events periodically into a pipeline ending up in some
single line for the
This isn't to do with Camel per se but I'm hopeful I'm asking this question
of the the right audience!
Basically we're going to be routing event messages into some storage
component where some of those messages may be billable to customers.
We have an existing service that charges customers
I'm not sure if the billing service needs the data from the business analysis.
If it doesn't need those data, it could be more easy by using wire-tap[1]
[1]http://camel.apache.org/wire-tap.html
--
Willem Jiang
Red Hat, Inc.
FuseSource is now part of Red Hat
Web: http://www.fusesource.com |
Hi James,
Very good and interesting use case. You could use BPM, indeed, but I
think it's way to heavy weight for what you need to do. CEP would be
another idea, but I digress.
Wire-tap won't help you, I believe Willem misunderstood your question.
So here's what I think: you have your
