EF read & write modes for CQRS
<p>I've read that Dapper is much faster than EF generally and was thinking about using Dapper for the query side and EF for the write side of an application using the CQRS (lite) pattern.</p>

<p>However, I'm also aware that EF has the ability to switch off tracking by default. Is it worth creating 2 database contexts, one for reading with AsNoTracking enabled across all entities, and one for writing with tracking enabled? This way I have the performance benefit without using another library and adding extra complexity.</p>