Hi Pablo, Thanks for your interest in the project and for the great proposal.
We are also considering distributing Siddhi using Kafka, we will consider your ideas when implementing the solution and we are happy to have your contributions. Meanwhile, have you done any implementation regarding this? Do you have any performance numbers? Currently, we are thinking of partitioning streams based on given stream attribute and process each partition in isolation, but your solution provides a simple state sharing technique to solve this problem. My only concern in your solution is, if the state change is frequent then this solution will not be optimal and the same problem is also there for the rolling aggregations as the window will be updated for each event. If we are syncing the state for each event then there will be a lot of overhead. Have you thought about it? Do you have any suggestions? Regards Suho On Mon, Dec 5, 2016 at 3:57 PM, Pablo Casares Crespo < [email protected]> wrote: > Hi all, the proposal as been attached as PDF. > > > > > > > Best regards, > Pablo. > > > _______________________________________________ > Architecture mailing list > [email protected] > https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture > > -- *S. Suhothayan* Associate Director / Architect & Team Lead of WSO2 Complex Event Processor *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 <http://lk.linkedin.com/in/suhothayan>*
_______________________________________________ Architecture mailing list [email protected] https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
