Ignite Compute (tasks, jobs, closure and etc.) provides API for distributed
computations. It is the main use case. Ignite Queue and Set is data
structures (as usual java set and queue but distributed). Ignite Messaging
can be used as inter-process communication.

Do you have use case and searching more appropriate tools for it? Can you
describe more concrete what you want?

On Fri, Jan 13, 2017 at 8:00 AM, zshamrock <aliaksandr.kaz...@gmail.com>

> What is the main use case for ignite Jobs
> (https://apacheignite.readme.io/docs/job-scheduling) and what they are not
> suitable for?
> It looks like Ignite has many concepts dedicated to the queueing/messaging:
> - https://apacheignite.readme.io/docs/job-scheduling
> - https://apacheignite.readme.io/docs/streaming--cep
> - https://apacheignite.readme.io/docs/queue-and-set
> - https://apacheignite.readme.io/docs/messaging
> Can someone summarize the exact use case for each of the above?
> --
> View this message in context: http://apache-ignite-users.
> 70518.x6.nabble.com/What-is-the-main-use-case-for-ignite-
> Jobs-and-what-they-are-not-suitable-for-tp10070.html
> Sent from the Apache Ignite Users mailing list archive at Nabble.com.

Reply via email to