On Thu, Jun 6, 2013 at 10:22 PM, Nuwan Dias <[email protected]> wrote: > 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 >
Yes it is possible to persist those to a DB. -- Rajeev Sampath Senior Software Engineer WSO2, Inc.; http://www.wso2.com. Mobile:* +94716265766 *
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
