Alexander, so if I understand well, you're running vert.x inside a Ignite node and use the vertx eventbus across the nodes for work distribution.
Our use case is financial order processing , where the web front-end layers ( outside the Ignite cluster ) will invoke a REST Api ( vert.x inside the cluster ) to handle the execution of orders. The Ignite cluster will be used to offload the back-end mainframes by : caching all customer information and handle the orchestration/workflow. The workflows for a single order will invoke multiple steps : collect additional information on authorization, verify authenticity of transactions, validate transactions in their context, update back-ends and provide status info on the order execution. Some of these workflow steps can be parallel executed , but need to be all successful to continue the order. So we are looking at the best way to handle these synchronization points and async event processing. Lieven > On 30-mrt.-2016, at 17:18, "alexGalushka [via Apache Ignite Users]" > <[email protected]> wrote: > > Lieven, > > We plan to have a cluster of 16 nodes and the dynamic node groups using > Ignite predicate. Each node will have the API Gateway, but only will be > active at a time (floating IP). API Gateway will manage incoming HTTP > requests. Each node is identical and will have same set of microservices. > Orchestration will happen in the sense that any node can process the job > depending on its current load. > > We'd like to talk to nodes directly using Ignite compute as well as send > vertx messages across the clustered event bus. > > Each node will be represented by a docker container with isolated JVM, > running one Vert.x instance. So we'll end up with one Ignite instance per > node. > > Check out Vert.x Ignite Cluster manage: > https://github.com/vert-x3/vertx-ignite > > I'm curious to hear about your use-case in more details as well:) > > --Alexander > > > If you reply to this email, your message will be added to the discussion > below: > http://apache-ignite-users.70518.x6.nabble.com/Orchestration-framework-Actor-framework-with-Apache-Ignite-tp3784p3791.html > To unsubscribe from Orchestration framework / Actor framework with Apache > Ignite, click here. > NAML -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Orchestration-framework-Actor-framework-with-Apache-Ignite-tp3784p3792.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
