Imagine we were the developers assigned to develop/handle concurrency in the blogging system, what would be the starting point for us? The analysis would provide us with an answer for what is required to handle concurrency. Most importantly, it would help us understand the concurrency conflict and how it needs to be handled.
We will explore how concurrency conflict occurs and what needs to be done to handle it. Finally, we will see how it has been handled by the EF Core team.
We need to visualize where we would be facing this issue, in general, when the user tries to update data that is stale, which means the underlying data in the database has changed since the object was filled. Then we have a problem that needs to be addressed before we go live. If we don't handle concurrency, then the user who updates it last would retain his change, overwriting the data updated by other users.
In a real-world application, no single user...