This question is locked. New answers and comments are not allowed.
When looking at the suggestions by Telerik how to incorporate DataAccess in a Web API project, I see their code example of instantiating a repository object with every invocation of the controller. Has anyone had any problems (like database table locking or similar issues) with this approach when the number of calls made to the Web API is more than a hand full?
1 Answer, 1 is accepted
0
Bernd
Top achievements
Rank 2
Rank 2
answered on 24 Jan 2017, 03:00 PM
Hi Guy.
I never had problems with that. As long as I didn't use async for write operations. That caused some trobule I wasn't able to resolve.
Using the Context API you can tell DataAccess how to handle concurrency if need be.
Regards
Bernd