Hi there, Firstly let me clarify that I am just an Ignite user - not an Ignite team member/expert...so it will be great to get the views of the experts in this discussion...
Now, in Ignite, all data gets 'stored' in a 'CACHE'. If you want your data to be persisted, you simply configure your designated Cache to have 'Persistance' set to enabled. Also there are various ways in which you can distribute your data among different nodes on a cluster. But for your basic use-case, you would probably set the 'Mode' configuration of your cache to 'REPLICATED'. This will ensure that all data arriving at any of your (2) nodes will be 'synced' to the other node. In an environment where your connection between datacenters is very good, like two AWS Availability Zones, the above scenario will probably give you satisfactory results. But if your inter-datacenter link is flaky as you mentioned, the above approach would not be recommended. For this scenario, you would probably be better off looking into GridGain's commercial (enhanced) version of Apache Ignite, which offers a specialised mechanism for Datacenter-Replication (over sub-optimal links). Hope this helps, Jose -- Sent from: http://apache-ignite-users.70518.x6.nabble.com/
