Hi Dev Team, I have attended recent Kafka Conference at LinkedIn Headquarter and you guys were doing something similar to what we are doing "Aggregated Call Graph across Many Web Requests" per Some interval.
We have Transaction Logging API Similar ( Think of it as Graph which stitch logs across many servers similar to http://devopsdotcom.files.wordpress.com/2012/11/screen-shot-2012-11-11-at-10-06-39-am.png and we have view similar to Network Tab in Chrome Inspect (call graph). We use end to end Kafka as Data Pipeline included Producer =>Brokers=>MM=>Brokers=>(Camus Job HDFS ). With Our transaction logs, we wanted to aggregate metrics(std,min,max, 1 to 99 percentile) etc across many Web Request. The person on Conf were taking about using Samza for doing this I just wanted to understand what is Back-end Storage and near-real time storage for this graph call and how Samza is better than Stream Processor such as Mupd8, and Storm. I would appropriate if you can share your experience... Thanks, Bhavesh
