Yep, I know !
The point was to have many concurrent updates, doing heavy jobs between fetching and saving.
I believe the fun runs inside the CubDB process and I did that in order to avoid serializing multiple updates. Am I wrong ?
Also I may use different repositories (ETS, CubDB, or Ecto) so the mutex is a simple way to queue updates to a common entity.
