Ayende @ Rahien

My name is Oren Eini
Founder of Hibernating Rhinos LTD and RavenDB.
You can reach me by phone or email:


+972 52-548-6969

, @ Q c

Posts: 6,026 | Comments: 44,842

filter by tags archive

RavenDB session management in ASP.Net Web API

time to read 1 min | 122 words

This was brought up in the mailing list, and I thought it was an interesting solution, therefor, this post.


A couple of things to note here. I would actually rather use the Initialize() / Dispose() methods for this, but the problem is that we don’t really have a way at the Dispose() to know if the action threw an exception. Hence, the need to capture the ExecuteAsync() operation.

For fun, you can also use the async session as well, which will integrate very nicely into the async nature of most of the Web API.



Just curious, I am fairly new to RavenDb and so far, I have seen that mocking is not the way we test along with RavenDb.

But in above case, don't we direct dependency on DocumentStore? For an ASP.NET Web API application which has unit testing in mind, what would you recommend?

Ayende Rahien

Tugberk, RavenDB can run in pure in memory mode, perfect for unit testing.


Had a similar question in mind - do you recommend firing up an in memory raven db per unit test or fire one up and use for a batch of tests. Is there any performance issue in firing up an in memory store (since using a fresh one per test would be purer).

Ayende Rahien

Ashic, We use one in memory store per test.

Ryan Riley

Why not create a DelegatingHandler and push that into your configuration? You can push the session object into HttpRequestMessage.Items. Was there a reason you chose to subclass ApiController instead?

Ayende Rahien

Ryan, It was the most obvious thing to do, this is similar to how I handle things in ASP.Net MVC

Comment preview

Comments have been closed on this topic.


No future posts left, oh my!


  1. Technical observations from my wife (3):
    13 Nov 2015 - Production issues
  2. Production postmortem (13):
    13 Nov 2015 - The case of the “it is slow on that machine (only)”
  3. Speaking (5):
    09 Nov 2015 - Community talk in Kiev, Ukraine–What does it take to be a good developer
  4. Find the bug (5):
    11 Sep 2015 - The concurrent memory buster
  5. Buffer allocation strategies (3):
    09 Sep 2015 - Bad usage patterns
View all series


Main feed Feed Stats
Comments feed   Comments Feed Stats