You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have a question regarding LiteDB's Concurrency Control. After reading the docs, I found that LiteDB is using one single writer per collection and multiple readers without locks. My question is:
How LiteDB guaranteed serializable reads without locks? What algorithm is used for this? I have checked the Index implementation and it seems to me that it's not thread-safe.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hi, LiteDb community!
I have a question regarding LiteDB's Concurrency Control. After reading the docs, I found that LiteDB is using one single writer per collection and multiple readers without locks. My question is:
Beta Was this translation helpful? Give feedback.
All reactions