after doing some tests with Siddhi and posting some questions on
stackoverflow... i would say thank you to all of you. I have learned a lot
reading this thread¡
So, i'm just trying to understand how Siddhi behaves when distributed is
enabled.
In my tests, i have checked that it does not replicate artifacts (queries,
stream definitions) through Hazelcast. Neither events, so i don't really
understand how the distributed mode works.
In StackOverFlow, Rajeev Sampath said that "it shares only events/state of
the engine. So in order to get this working, you'll have to first separately
synchronize these queries/stream definitions across all Siddhi instances in
your distributed setup. Once you have those in place, you'll be able to get
it working in distributed mode."
But then,
1) Which benefits have this solution? what's the real purpose of current
distributed mode?
2) Why or when i should use this kind of deployment?
3) Ok, I could sinchronize queries/stream definitions between different
siddhiManagers, but if i have a time window how does it would work in
distributed mode? each engine would have its own window? or is there a
global window?
Thanks.
--
View this message in context:
http://wso2-oxygen-tank.10903.n7.nabble.com/A-few-questions-about-WSO2-CEP-Siddhi-tp93070p94584.html
Sent from the WSO2 Architecture mailing list archive at Nabble.com.
_______________________________________________
Architecture mailing list
[email protected]
https://mail.wso2.org/cgi-bin/mailman/listinfo/architecture
