Hi, Here are my answers.
0. Not sure about production usage, but the described approach makes sense to me. 1. Ignite is designed to be scaleable, so you just need to make sure that you have enough memory for your data. Refer to [1] for information about capacity planning. 2-3. You can simply deploy a node singleton service [2] and Ignite will guarantee that there is always an instance of the service on each node. If a new node joins, it will be deployed there automatically as well. [1] https://apacheignite.readme.io/docs/capacity-planning [2] https://apacheignite.readme.io/docs/service-grid -Val -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-CEP-tp6497p6568.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
