Is it good practice to have multiple data contexts?

Question

When parsing a solution into multiple projects, does it make sense to have multiple data contexts or use a context?

Example: for a web portal you have:

App.Service1
App.Service2
App.Web (references Service1 and Service2)

Now do you have this so that Service1 and Service2 share the same DataContext, or each of them has its own?

Keep in mind that both Service1and Service2are connected to the same database, they simply divided to make things more isolated.

I am using EF6.

Answer 1

. , .

Answer 2

, Entity Framework ,

, , , Service1 Service2 .

, , .

Answer 3

, , , , () , , , , . , . .

Answer 4

. , , EF , . , @Darin.