Ultimately it depends on the architecture of your application or use case. If you are considering deploying a set of "central" or dedicated Ignite nodes, it makes little sense to embed Ignite into an app on those nodes – you may run it standalone. If your architecture is fully decentralised, you can rely on embedding Ignite into your application on all nodes. Take into account that if you're running compute jobs, you'll have to deploy the class definitions on the standalone nodes – or you can use peer-classloading.
Cheers, *Raúl Kripalani* PMC & Committer @ Apache Ignite, Apache Camel | Integration, Big Data and Messaging Engineer http://about.me/raulkripalani | http://www.linkedin.com/in/raulkripalani Blog: raul.io | twitter: @raulvk <https://twitter.com/raulvk> On Thu, Mar 3, 2016 at 6:28 AM, 上帝已死 <[email protected]> wrote: > 1. Embed to application by maven. > 2. Launch a bin file.(I don't know how to operate cache. By Http Api?) > Which one is better? > > > > -- > View this message in context: > http://apache-ignite-users.70518.x6.nabble.com/Which-way-to-use-ignite-is-better-tp3350.html > Sent from the Apache Ignite Users mailing list archive at Nabble.com. >
