Transactions and atomicity
Hi all! I'm researching JanusGraph and I'm excited to learn more. There's one thing I haven't understood when using JanusGraph with a storage backend like ScyllaDB:
According to the docs, the best way to avoid data inconsistencies is to use a storage backend that supports atomic batch writes. If I do that, do I remove all risk of half-edges and other permanent inconsistencies -- i.e. is eventual consistency guaranteed? And if the storage backend does support atomic batch writes, how can I tell if JanusGraph actually uses it?
According to the docs, the best way to avoid data inconsistencies is to use a storage backend that supports atomic batch writes. If I do that, do I remove all risk of half-edges and other permanent inconsistencies -- i.e. is eventual consistency guaranteed? And if the storage backend does support atomic batch writes, how can I tell if JanusGraph actually uses it?