Vitess offers different transaction modes and isolation levels as described
here: http://vitess.io/user-guide/twopc.html#isolation.

The choice depends on what an application can tolerate. In case of the
current Vitess community, users have rarely requested 2pc. They are usually
satisfied with single-shard ACID transactions. The few that have requested
2PC are satisfied with the default isolation trade-offs.

On Tue, May 16, 2017 at 1:46 PM, Alexis Richardson <alexis@...>
wrote:

This transition: X --> scalable X, suggests we are seeing parallel
evolutions of each category X. If so then we can ask what properties
of X are preserved. Atomicity and durability only?

On Tue, May 16, 2017 at 9:31 PM, Brian Grant <briangrant@...>
wrote:

Again, the main value as I see it is that Vitess facilitates a
transition
from MySQL to a more scalable implementation (scalable enough for
Youtube),
without taking so big a leap as NoSQL. Sugu confirmed that Vitess is
getting
interest from MySQL users.

I could imagine also trying to find projects covering other categories,
such
as object storage and some flavor(s) of NoSQL.

I view filesystems as a different category than these application-level
storage systems.

On Tue, May 16, 2017 at 8:29 AM, Alexis Richardson via cncf-toc
<cncf-toc@...> wrote:

The main doc:



https://docs.google.com/document/d/1p7gqlpQNJpZtsolHeX6vXR4NXXwGrCMsCz8rSi5jsBA/edit#heading=h.d6b07oufwoag

The original presentation a few weeks ago:



https://docs.google.com/presentation/d/1hvTin7ui_p_klCM9F88vBoFU_5K4Ax6KlnYIZR5jAgs/edit#slide=id.gd5ae4e962_2_136
_______________________________________________
cncf-toc mailing list
cncf-toc@...
https://lists.cncf.io/mailman/listinfo/cncf-toc