Daniel Marbach & Mauro ServientiMicrosoft MVP

http://particular.net

Asynchronous Messaging with NServiceBus

2

Introduction to ServiceInsight for NServiceBusScaling with Asynchronous Messaging

The VETRO pattern

Message queue architecture

Recap

Introduction to ServiceInsight for NServiceBusScaling with Asynchronous Messaging

Integration pattern –

receive input; process;

send output.

Discrete components.

Well suited to distributed

processing.

The VETRO Pattern

Validate

Enrich

Transform

Route

Operate

Introduction to ServiceInsight for NServiceBusScaling with Asynchronous Messaging

Single host receives input &

sends 'do processing'

messages to queues.

Hosts can read from

queues without contention.

Allows multiple hosts to run

processing concurrently.

More scale – add hosts.

Message Queue Architecture

Introduction to ServiceInsight for NServiceBusScaling with Asynchronous Messaging

Demo: App V2

Asynchronous message sending

Single producer process

Multiple consumer processes

This time with NServiceBus

Demo

Introduction to ServiceInsight for NServiceBusScaling with Asynchronous Messaging

•NServiceBus reduces boilerplate code•NServiceBus brings in battle tested

queue infrastructure code•NServiceBus provides in addition to that

• First Level Retries• Second Level Retries• Auditing and more

•NServiceBus is part of a richer platform

Summary

Thank you

github.com/mauroservienti/going-async