@@FranckPachot consistent reads can be solved by either lookup to leader replica or look up to 2 replica and get the latest record, {forgetting the design choice here.} Adding trns Manager altough guarentee consistent view but it will add another hop at request path.
![[TH] 2024 PMGC League | กลุ่มสีเหลืองวันที่ 1 | PUBG MOBILE Global Championship](http://i.ytimg.com/vi/I_FdxGT3WV4/mqdefault.jpg)
![[LIVE] : ONE ลุมพินี 85 | คู่เอก "ยอดเหล็กเพชร vs ผึ้งหลวง"](http://i.ytimg.com/vi/Qq_19bnnxEo/mqdefault.jpg)
excellent material !!!
Good idea. Looks like RDBMS + NoSQL on Hadoop architecture though.
Why Trns manager needs to be there for read path.
I thought trns manager only helps for ACID trans. ?
Because you want to read a consistent view of the data. Secondary Indexes, joined tables, ... all from the same state
@@FranckPachot
consistent reads can be solved by either lookup to leader replica or look up to 2 replica and get the latest record, {forgetting the design choice here.}
Adding trns Manager altough guarentee consistent view but it will add another hop at request path.
@@pankajbhardwaj2463 MVCC might query on historical data like repeatable read. A consistent read point should be asked from somewhere.