On Thu, Jun 6, 2013 at 3:28 PM, Sriskandarajah Suhothayan <[email protected]>wrote:
> > > > On Thu, Jun 6, 2013 at 3:10 PM, Vijayaratha Vijayasingam > <[email protected]>wrote: > >> Hi; >> APIM team has different kind of throttling+rate limiting requirements >> (eg:ip/timer/geo based)..As Srinath pointed we believe that CEP would be >> the right solution, since we cannot have all these different >> scenarios/requirements to be implemented in our throttling module.. >> Is there any possibility integrate CEP engine with our throttling module ? >> > > Yes this is possible > Currently you can use Siddhi directly to achieve this. In this case you > have to pass all the events the trigger throttling directly to Siddhi and, > when a matching throttling condition reached CEP will fire an output back > to APIM so that it can take action based on the CEP's response. > How feasible is it to run Siddhi as an embedded engine within APIM? I am thinking along the lines of avoiding an additional hop between the API Gateway and CEP. Is it also possible to persist the throttling information to a database? Probably not on every request but batch by batch > > With CEP 3.0.0 we are writing an Event Processor component( as of mail > thread "CEP 3.0 towards a Complete eventing solution to the platform"), > when that is done you will also be able to provide a proper UI for the > users to edit Siddhi throttling queries > > > So, all products can still use throttling module, which can handle all the >> complex rate/thorrtling policies.. >> > > +1 > > > Suho > > > >> Thanks >> >> >> On 5 June 2013 15:13, Sriskandarajah Suhothayan <[email protected]> wrote: >> >>> >>> >>> >>> 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 >>> >>> >> >> >> -- >> -Ratha >> mobile: (+94)755906608 >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > *S. Suhothayan > * > Associate Technical Lead, > > 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 > > -- Nuwan Dias Senior Software Engineer - WSO2, Inc. http://wso2.com email : [email protected] Phone : +94 777 775 729
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
