Local and available reads see only majority data
What changes in Local and available reads see only majority data compared with MongoDB and what your application has to do.
This difference is of the Stronger guarantee kind.
What MongoDB does
With readConcern local or available you can read a w: 1 write that can still be lost.
What TeselaDB does
Those reads always return data confirmed by a majority. They see what was confirmed to the client before they started. If a range loses its majority with a write pending, the read waits until it is resolved.
What your application has to do
Nothing. You no longer need majority to avoid seeing writes that can be lost.