The intro to this ACID section contradicts itself - it says both that "geode does not provide applications a rigid adherence to all the ACID properties" and "geode results in much higher transaction performance without sacrificing ACID promises."
I would say that geode transactions do provide ACID. However, we provide durability through the use of redundancy rather than disk persistence. The one fuzzy bit might be the isolation - however every database seems to have different isolation levels. We just need to provide a clear description of the level of isolation we provide with respect to dirty reads, etc. This might be a good place to link to the caveat's about queries. The fact that geode uses optimistic transactions does not affect the ACID properties of the transaction, so maybe that should be in a separate section about "Optimistic transactions?" That's probably the most important thing someone coming from a different transactional system needs to know about geode transactions. [ Full content available at: https://github.com/apache/geode/pull/2304 ] This message was relayed via gitbox.apache.org for [email protected]
