Date
1 - 5 of 5
prior docs about vitess
|
alexis richardson
|
|
|
|
Brian Grant
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: |
|
|
|
alexis richardson
This transition: X --> scalable X, suggests we are seeing parallel
toggle quoted message
Show quoted text
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 |
|
|
|
Sugu Sougoumarane
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 |
|
|
|
alexis richardson
thanks Sugu - that is helpful.
toggle quoted message
Show quoted text
If we are going to ask Kyle if he could 'do a jepsen', it would be very good to understand which consistency choices should be tested. On Tue, May 16, 2017 at 11:59 PM, Sugu Sougoumarane <sougou@...> wrote:
Vitess offers different transaction modes and isolation levels as described |
|
|