Page History

...

1. Strong isolation
2. Support for interactive transactions
3. Conflict resistance
4. Read-only (long lived) transactions
5. Consistent replica reads
6. Optimized for fast path execution
7. Geo-distributed clusters supportdistribution aware
8. Unlimited or very large transaction size
9. Transactional DDL
10. Data loss toleration

...

We can try to optimize the protocol to handle common scenarios better.  For example, small sized transactions can be optimized by buffering writes until a commit to reduce lock held time. I measure it with 1

Geo-distribution

...

aware

Geo-distributed clusters are gaining popularity. While they suffer from network latency issues due to light of speed limit, they are the best for high availability. So, the protocol should minimize a number of messages send between regions. I measure it with 2

...

Nice to have, can help with migration scenarios. I measure it with 1

...

Data loss toleration

It's important to know how many node failures we can tolerate until declaring the unavailability due to temporary data loss (or full in case of in-memory deployment). More is better. I measure it with 2

...