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,128 | Comments: 45,548

filter by tags archive

Batching WCF Calls

time to read 1 min | 156 words

Several months ago I wrote about how I think you should design your services. The key criteria was that they have to have a batch mode enabled.

Afterward, I put together a screen cast that goes through all the stages that led me to that stage.

Davy Brion has taken this approach a bit further and posted all the infrastructure bits that are required to make this work as well as what you need to actually make the API almost as nice to use as the non batched version.

The service API is here and the client API is here.

About the only thing that I would strive to improve there would be the need to explicitly register request & replies. I would try to get something convention based there. Maybe something like Request<TRespose>, and then have IHandler<TRequest> and route the whole thing through the container again.


Davy Brion

yea i'm not happy with the explicit registering either... i really want something better there so i'll look into your suggestion ;)


I like the way it is done in NServiceBus - all you need is three interfaces (IMessage, IHandler, IBus). Just substitute the IBus for your IService and your done. Why bother to add specific service interfaces like IProductsService?

The interface IHandler has another advantage - one class can implement many of these, so you can have e.g. all product messages handling code in one class (you don't need one class per message anymore).

Davy Brion

the specific service interfaces are there in case you prefer to just call one specific method... it's also good for 'discoverability'

i actually like to have one class per message. depending on how many messages you have regarding products, it could be a huge class if you handled all of them in the same class. Also, one class per message makes it really easy to have the container inject each dependency you need

Davy Brion

ok, now you no longer need to explicitly register Requests & Replies

you can find the new implementation here:


Comment preview

Comments have been closed on this topic.


  1. The low level interview question - 9 hours from now
  2. The worker pattern - 3 days from now

There are posts all the way to May 30, 2016


  1. The design of RavenDB 4.0 (14):
    26 May 2016 - The client side
  2. RavenDB 3.5 whirl wind tour (14):
    25 May 2016 - Got anything to declare, ya smuggler?
  3. Tasks for the new comer (2):
    15 Apr 2016 - Quartz.NET with RavenDB
  4. Code through the looking glass (5):
    18 Mar 2016 - And a linear search to rule them
  5. Find the bug (8):
    29 Feb 2016 - When you can't rely on your own identity
View all series



Main feed Feed Stats
Comments feed   Comments Feed Stats