On Thu, May 9, 2013 at 4:33 PM, Jaime Nebrera <[email protected]>wrote:
> ** > Hi Srinath, > > Maybe my explanation was not that good. > > As said, we are interested mainly in the CEP side, but at the same time, > it could be a great oportunity to get to know better WSO2 platform and use > other components too. > > We dont want to change the way the "events" are managed internally, but > to provide a "bridge" to comunicate WSO2 with "external world", but in both > directions, that is, be able to inject events but also to "produce" events > in Kafka format. > > In an ideal world, Kafka events would be injected into WSO2, transformed > in whatever internal format you have, get filtered, go through business > rules, go to CEP, produce its own events and get them outside again in > kafka format. If in the middle they raise a trigger or are stored in > Cassandra or whatever, is not our goal. > > Also, th eproject is not that urgent, thus if you say you need to sovle > first an specific issue but once there the best way would be to work with > XYZ, thats is ok > > We are just trying to think in advance before doing the real coding and > your info on CEP is just very interesting, specially the fact you do > horizontal scalability right away while Esper requires a "proprietary" > extension > > We were thinking about using Twitter's Storm too for some of the > "routing / filtering" stuff (no CEP, I'm aware of that) but seems WSO2 > could fit all that too, so its worth a try > > > You can find the extension point to connect external transports to WSO2 CEP here[1] This also has a link to a sample, I believe this will be a good starting point to send and receive Kafka events to & from WSO2 CEP. Suho [1]http://docs.wso2.org/wiki/display/CEP210/Writing+Custom+Broker On 09/05/13 12:33, Srinath Perera wrote: > > Hi Jaime, > > CEP Server has something called brokers. That is one way to do this. You > can write a Kafka based broker, and inject events to CEP. > > But that works only with CEP, and to support other part of the platform > (e.g. send it to ESB for mediation, service invocation etc), you will have > to write a Axis2 transport. > > Currently we are working to make Axis2 transport work for both cases, > but that is in the trunk. It may be easier to start with a broker as then > you do not have to worry about converting to XML (there is a way to work it > without converting to XML, but bit too complex yet, which we are fixing > now). > > > --Srinath > > > On Thu, May 9, 2013 at 1:07 AM, Jaime Nebrera <[email protected] > > wrote: > >> Hi all, >> >> We would like to add Apache Kafka support to the already long list of >> supported protocols of WSO2 in order to be able to exploit CEP capabilities >> >> Were would be the right place to do so in order to, not only get Shiddi >> CEP capabilities but also be able to use other elements of WSO2 and of >> course make our contribution worthwhile and interesting to others >> >> BTW, I have been unable to find any reference to such project. Nobody >> has considered this alternative in the past? >> >> Thanks and regards >> >> Jaime Nebrera - ENEO Tecnología >> Sent with mobile, sorry for typos >> >> _______________________________________________ >> Architecture mailing list >> [email protected] >> https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture >> >> > > > -- > ============================ > Srinath Perera, Ph.D. > http://www.cs.indiana.edu/~hperera/ > http://srinathsview.blogspot.com/ > > > _______________________________________________ > Architecture mailing > [email protected]https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > > > -- > Jaime Nebrera - [email protected] > Consultor TI - ENEO Tecnologia SL > C/ Manufactura 2, Edificio Euro, Oficina 3N > Mairena del Aljarafe - 41927 - Sevilla > Telf.- 955 60 11 60 / 619 04 55 18 > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *S. Suhothayan * *Software Engineer, Member, Management Committee - Data Technologies Team, * * * *WSO2 Inc. **http://wso2.com <http://wso2.com/>* *lean . enterprise . middleware* *cell: (+94) 779 756 757 blog: **http://suhothayan.blogspot.com/* <http://suhothayan.blogspot.com/>* twitter: **http://twitter.com/suhothayan* <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
