Hi, Please properly subscribe to the user list, so everyone in the community could get the notifications. All you need to do is sent an empty email to "[email protected]" and follow the instructions in the reply.
andy@bdp wrote > I need to create an architecture for Ignite that allows: > > Data to be streamed into a cache. You will likely need to use IgniteDataStreamer API for this. andy@bdp wrote > A cache listener to put selected entries in a queue. One or more > distributed processes to wait for queue entries, do some work and put the > results back in a cache. The streamer comes with StreamReceiver which allows you to process the data before it gets put in a cache. I am not sure what you mean by processing "waiting" for queue entries. Would it be sufficient to have this processes implement their logic in the StreamReceiver? andy@bdp wrote > Also, point me in the direction of an example(s) of a listener putting > something on a queue and 1 or more processes consuming the queue entries. Ignite comes with many examples. I think in your case you should take a look at the streamer examples here: https://github.com/apache/ignite/tree/master/examples/src/main/java/org/apache/ignite/examples/streaming https://github.com/apache/ignite/tree/master/examples/src/main/java8/org/apache/ignite/examples/java8/streaming andy@bdp wrote > Does anyone have a sample architecture diagram that Ignite conforms to? There are many architectural diagrams in the documentation. If you are asking how the keys are distributed, perhaps you will find this documentation useful: https://apacheignite.readme.io/docs/cache-modes -- View this message in context: http://apache-ignite-users.70518.x6.nabble.com/Ignite-architecture-tp1588p1595.html Sent from the Apache Ignite Users mailing list archive at Nabble.com.
