Hi Samisa, +1, in any case to support monitoring reasonable large number of servers with BAM we should create the batch mode. Basically get the data publishers cache all collected data, and publisher sends them in only once few seconds. In a more advanced version, high priority events will trigger a immediate transfer while low priority events are transfer in batch fashion.
Thanks Srinath On Wed, Aug 4, 2010 at 6:23 AM, Samisa Abeysinghe <[email protected]> wrote: > In order to solve the problem of message volume burst in in case of message > level data collection like in the case of counting activity ID, we are going > to introduce a batch mode, where we collect information on several messages > and fire an event together for all those based on a message count > threshold. > This is the simplest and the fastest solution to burst problem we have now. > > Advanced solutions like queue based models can be take up later, but I doubt > the need of those if this works well for us. > > Thanks, > Samisa... > > Samisa Abeysinghe > VP Engineering > WSO2 Inc. > http://wso2.com > http://wso2.org > > > > _______________________________________________ > Carbon-dev mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- ============================ Srinath Perera, Ph.D. WSO2 Inc. http://wso2.com Blog: http://srinathsview.blogspot.com/ _______________________________________________ Carbon-dev mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
