There’s nothing “out of the box” I’m afraid. There are commercial options available.
With open source, it would be relatively straight-forward to copy changes over using something like Kafka. Or, assuming you’d want it to be event-driven, you could listen to the first cluster with a thick client, publishing to the second using a thin-client. The challenge in both cases comes in making sure the two stores stay in sync in the event of outages/downtime. > On 14 Oct 2020, at 11:07, steve.hostettler <steve.hostett...@gmail.com> wrote: > > Hello and thank you for your answer. > > Assuming we would have 2 clusters (e.g., we want to scale them > independently, upgrade them at different pace) that are manipulating > different datasets. The output of the first clusters being the input of the > second one. > > > > > > -- > Sent from: http://apache-ignite-users.70518.x6.nabble.com/
