1. Introduction to NServiceBus
Daniel Marbach
Co-Founder of .NET Usergroup Zentralschweiz
Co-Founder planetgeek.ch
Founder of Enthusiasm Driven Development

2. bbv Software Services AG
Quick Facts
• Dienstleistungsunternehmen
• 150 Mitarbeitende
• KMU-Strukturen – schnell, direkt, AGIL
Arbeiten in der Schweiz Permanents:
• kameradschaftlicher Umgang
• Hoher Verdienst, geringe Steuern
• Arbeiten, wo andere Urlaub machen … Freelancer:

3. This is your last chance. After this, there is no turning back.
You take [you name it] - the story ends, you wake up in your bed
and believe whatever you want to believe.
You take NServiceBus - you stay in Wonderland
and I show you how deep the rabbit-hole goes.

4. The only rule to
remember

5. If it is complicated
you’re probably doing it wrong

7. More reliable than regular WCF or HTTP
style service communication
Open-source Service Bus
Flexible publish / subscribe
Durable long-running processes

8. Service Bus

9. App App
Bus.dll Bus.dll
App App
Bus.dll Bus.dll
App App
Bus.dll Bus.dll
App App
Bus.dll Bus.dll

10. No single point of failure

11. Not necessarily physically separate
Channels are both physical and logical

12. Communication is dispersed over
multiple channels

13. Simpler than a broker
no routing or service fail over

14. Get on the bus?

15. Reliability

16. [HTTP] $$ Order
Call 1 of 3
DB
App Tx Call 2 of 3
Crash / Deadlock / other
Where’s the order!? Rollback

17. DTC
TX Receive Rollback
$$ Order Q ESB
Invokes
Rollback
Call 1 of 3
Your DB
Call 2 of 3
code
The order is back in the queue

18. Throughput
Messaging
RPC
Load

19. Try
Success
Do
And Again
Fail
Fail
Do Again

20. Publish / Subscribe

21. Service A Service B
MakeCustomerPreferred()
Customer GetCustomerInfo()
Waiting Working
Return
Return

22. Service A Service B
Publish updated customer info
Store data
MakeCustomerPreferred()
Save customer
as preferred
Publish Customer made
preferred

23. Subscriber must be able to make decisions
based on somewhat stale data

24. Strong division of responsibility between
publishers and subscribers

25. Only one logical publisher should
be able to publish a given kind of event

26. Assume that messages may
arrive out of order

27. Function Webservice
Class Database

28. Business Data &
capability Business Rules
Everything Nothing left
is contained over

29. Explicit Boundaries
Autonomous
Policy Policy
Contract & Schema

31. Long-running process

32. Start Saga Create Saga For Message
Message
Dispatch Message
Saga
Bus
Send Saga Messages
Save Saga
Saga
Persister
DB Persist

33. Saga Message
Get Saga by Message.SagaId
4.Return Saga
2.New
Dispatch Message
3.Fill
Saga
Bus Saga
Persister
Complete
Saga Complete
Timeouts are regular 1.Get Delete
messages
Can occur on multiple
machines concurrently
DB

34. Use sagas inside service boundaries

35. Domain Models are Sagas

36. Sagas allow to model Timeouts
of your business processes

39. Which pill do you take?
nservicebus

40. Thanks for listening
Special thanks to
Udi Dahan and NServiceBus Ltd.
for supporting me
Daniel Marbach
dotnet-zentral.ch
planetgeek.ch
appccelerate.com
@danielmarbach

41. Links
Copyright of Images
www.sxc.hu
Websites
nservicebus.com
udidahan.com
andreasohlund.net