thanks Dmitry.
looks like i need to stick to distributed Queue as it supports replicated
backup copy.
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Yes, you can have backup copies of data in caches.
At the same time you can have several message listeners set up on several
nodes being .
About topic message instance itself, there is only one copy of message in
cluster. So particlar message may be lost in some cases of node failure.
This is
Thanks.
Can it have extra backup copies in Ignite Cluster (for HA or fault
tolerance) ?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Yes, I use it. It works well.
Sent from my iPhone
> On 16/03/2018, at 2:56 AM, piyush wrote:
>
> Has anybody used this feature ?
>
>
>
> --
> Sent from: http://apache-ignite-users.70518.x6.nabble.com/
Has anybody used this feature ?
--
Sent from: http://apache-ignite-users.70518.x6.nabble.com/
With Regards to "Topic Based Messaging" mentioned in official doc here
https://apacheignite.readme.io/docs/messaging
Can it be a distributed alternative to Apache Kafka ?
Can it have extra backup copies ?
Can it use disk persistence with extra backup copies on another node just
l
ite server and other as
> client. Can I reply on Ignite Topic Based Messaging for sending messages
> from client to server? What would happen when server is down or restarting
> and client wants to send a message?
>
> Are these topics durable? Will it store message till the time