I have N (>1) web servers managed by a load balance-r and 1 instance of SQL DB as a data store in the backend. The data is read from DB, users edit it, and updated data is sent back to DB. I'm using Linq-to-Sql. If it's a single web server, the concurrency control provided by LinqToSql is good, but with this setting, what's the good way to detect concurrent edits to the data?
Asked
Active
Viewed 202 times
1 Answers
0
Entity Framework should do the trick. For both Pessimistic Concurrency (Locking) & Optimistic Concurrency.
See here for a clear example and keep in mind to clearly identify which strategy is more appropriate for you.