notes from a passionate developer





This is a personal blog. The opinions expressed here represent my own and not those of my employer, nor current or previous. All content is published "as is", without warranty of any kind and I don't take any responsibility and can't be liable for any claims, damages or other liabilities that might be caused by the content.

Routemeister and middlewares

Today I released v0.3.0 of Routemeister, where I added a new router that allows you to hook in middlewares in a way similar to how you can to in Owin. This means, you e.g. can intercept, wrap or exit the pipeline before the message is routed to its handler.

Use the new router

First lets get som routes:

var factory = new MessageRouteFactory();
var routes = factory.Create(fromAssembly, typeof(IMyHandler<>));

Now, instead of SequentialAsyncMessageRouter you use MiddlewareEnabledAsyncMessageRouter:

var router = new MiddlewareEnabledAsyncMessageRouter((t, e) =>
router.Use(next => async msgEnvelope =>
        await next(msgEnvelope );
    catch (Exception ex)

router.Use(next => async msgEnvelope =>
    if(msgEnvelope.MessageType == typeof(Foo))
    await next(msgEnvelope );

Now, whenever you route a message, it will be passed to the middlewares:

await router.RouteAsync(new MyMessage { Score = 42 });

You don't need a router

Remember, you don't have to use a router to use Routemeister. All you need are the routes:

var route = routes.GetRoute(messageType);
var routeAction = route.Actions.Single();
var messageEnvelope = new MessageEnvelope(myMessage, messageType);

await routeAction.Invoke(handler, messageEnvelope);

That's it. You can read more about a use-case in where this is used with Autofac, to create child lifetime scopes, and thereby per-request resource scoped messages being routed.


View Comments