Thanks Dmitry. Based on the scenarios I have to deal with (for the time being at least), using Ignite distributed cache should ne avoided.
However the issue now is that my callables will have to use Spring beans (services and DAOs) in order to retrieve on their own the data that they have to process when run() is executed. In order to do this, I read that I must define Spring Application Context as *transient* in my Callable class which extends IgniteCallable. Then, inside run() I can get local references of the Springs beans I need and use them normally. The thing is that if I go this way, I can no longer simply start nodes by command line script (ignite.sh / ignite.bat). I will either have to start Spring as web application deployed in e.g. Tomcat at each node using IgniteSpringBean or to create a class with Main method which will load the application context and launch it with *java -jar*. Am I correct or is there a more flexible way? I not here that my main web application which is the one that triggers the distributed computations is based on Spring 5. Thank you. -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Distributed-callables-passing-data-and-getting-back-results-tp11224p11344.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
