I was part of this during my internship at amazon this tear. Learned a lot, contributed a bit.Hope to get a return offer soon to continue working on it.🤞
Amazing! Really pushing the boundaries with what a relational DB can do. I would be curious to know if sharded tables can take advantage of autoincrement indices. (serial or bigserial).
Vitess utilizes a two-phase commit mechanism for transactions, which guarantees atomicity, yet it does not assure distributed consistency. This aspect constitutes a major difference in the context of sharded databases.
I was part of this during my internship at amazon this tear. Learned a lot, contributed a bit.Hope to get a return offer soon to continue working on it.🤞
All the best mate :)
Amazing! Really pushing the boundaries with what a relational DB can do. I would be curious to know if sharded tables can take advantage of autoincrement indices. (serial or bigserial).
Is the information presented here made public? If so where can we find the slides presented in this video?
Hello, 👋 although I don't have a timeline, the event content from re:Invent will be available here: go.aws/416SDuN. ^AD
Sounds similar to Vitess on Aurora
Vitess utilizes a two-phase commit mechanism for transactions, which guarantees atomicity, yet it does not assure distributed consistency. This aspect constitutes a major difference in the context of sharded databases.
Concepts of limitless sounds very similar to TiDB
TiDB was released in 2017, to me this looks like Spanner that was released in 2012, it has this timestamp based consistency