Re: Would this be crazy?

2016-01-18 Thread nino martinez wael
The idea are that we will have 2 nodes per call in a telephony setup.. A primary node for external service calls and a secondary node to follow the call around the system (agent/humans).. This however can amount a lot.. On Mon, Jan 18, 2016 at 2:40 PM, Alexey Kuznetsov

Re: Would this be crazy?

2016-01-18 Thread Alexey Kuznetsov
Hi, Nino! I think it is quite crazy idea to setup 1000 concurrent clusters (if I understand you correctly). Starting 1000 nodes will be quite expensive. Could you please describe what business logic you are going to implement? It is not clear for me what are you expecting from Ignite and what

Would this be crazy?

2016-01-18 Thread nino martinez wael
Hi We are considering using Ignite as a backend for our client / server environment (for Ignites key/value store). IT's a telephony based system, and the idea are that as a telephony CALL passes through the system Ignite nodes will follow the call adding and manipulating data. Each call would

Re: Would this be crazy?

2016-01-18 Thread Alexey Goncharuk
Nino, Can you please elaborate why you want to start several nodes per call in your architecture? Generally, the number of nodes is a factor of number of machines you have, in rare cases you may need to start an Ignite client per external call, however, usually it is not very effective. If you