On Wed, Jun 5, 2013 at 1:27 AM, Srinath Perera <[email protected]> wrote:
> Hi All, > > Currently we have a java based throttling solution. But we need that to > extended (e.g. support throughput based throttling), and support more > complicated condition that currently parameterized. > > IMO, best way to do this is to support this by integrating CEP (Siddhi) > engine directly at java level. It is very light weight . We can let users > provide CEP queries which will control throttling. Basically, there will be > inbuilt event stream definitions, and Siddhi listener that monitors a given > event stream and adjust event acceptance. Users provide CEP queries. > > I think it is too heavy publish events via thrift API if we try to send it > via the network. > > WDYT? > +1 CEP team can provide the necessary support if any of the product teams (eg: ELB, BPS, AF or AM) is willing to replace their current or have an alternate throttling module Suho > > --Srinath > > -- > ============================ > Srinath Perera, Ph.D. > Director, Research, WSO2 Inc. > Visiting Faculty, University of Moratuwa > Member, Apache Software Foundation > Research Scientist, Lanka Software Foundation > Blog: http://srinathsview.blogspot.com/ > Photos: http://www.flickr.com/photos/hemapani/ > Phone: 0772360902 > -- *S. Suhothayan * Software Engineer, Management Committee Member, Data Technologies Team, *WSO2 Inc. *http://wso2.com * <http://wso2.com/>* lean . enterprise . middleware *cell: (+94) 779 756 757 | blog: http://suhothayan.blogspot.com/ twitter: http://twitter.com/suhothayan | linked-in: http://lk.linkedin.com/in/suhothayan* * *
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
