Some quick advices for Entity Framework in a multi-threaded environment:
- Don’t use a unique context with
locks(no singleton pattern)
- Provide stateless services (you need to instantiate and dispose one context per request)
- Shorten the context lifetime as much as possible
- Do implement a concurrency-control system. Optimistic concurrency can be easily implemented with Entity Framework (how-to). This will ensure you don’t overwrite changes in the DB when you use an entity that is not up-to-date
I’m a bit confused, I thought that using one context is good because
it does some catching I believe, so when I’m dealing with the same
entity in consecutive requests it be much faster to use the same
context then creating a new context every time. So why does it good to
use it like this if It slower and still not thread safe?
You could use only one context, but it’s strongly discouraged unless you really know what you are doing.
I see two main problems that often happen with such an approach:
you’ll use a lot of memory as your context will never be disposed and all manipulated entities will be cached in memory (each entity that appears in the result of a query is cached).
you’ll face lots of concurrency issues if you modify you data from another program/context. For example, if you modify something directly in your database and the associated entity was already cached in your unique context object, then your context won’t ever know about the modification that was made directly in the database. You’ll work with a cached entity that is not up-to-date, and trust me, it’ll lead to hard-to-find-and-fix issues.
Also don’t worry about performances of using multiple contexts: the overhead of creating/disposing a new context per request is almost insignificant in 90% of use cases. Remember that creating a new context does not necessarily create a new connection to the database (as the database generally uses a connection pool).