Consistency

Mapfs supports final consistency.

If Mapfs is deployed in a cluster environment, the synchronization latency depends on the cache timeout policy.

By default, the cache timeout is 5 minutes, and that's logically the upper time latency for data changes to be synced to another mapfs client. Of course, you can reduce the cache timeout from 5 minutes to 10 seconds for example, then the maximum time latency for one mapfs client realized the data changes from another mapfs client is 10 seconds.

Anyway, mapfs doesn't support real-time synchronization. So, consider your workflow schema, if real-time sync is mandate, mapfs doesn't applies to. Otherwise, mapfs is a better choice.