Your SlideShare is downloading. ×
NServiceBus workshop presentation
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

NServiceBus workshop presentation

1,071

Published on

Espen Ekvang and I had a one day workshop internally at BEKK, and this is the presentation we made for the workshop.

Espen Ekvang and I had a one day workshop internally at BEKK, and this is the presentation we made for the workshop.

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,071
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
34
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • The Fallacies of Distributed Computing are a set of assumptions that Peter Deutsch and others at Sun Microsystems originally asserted programmers new to distributed applications invariably make. These assumptions ultimately prove false, resulting either in the failure of the system, a substantial reduction in system scope, or in large, unplanned expenses required to redesign the system to meet its original goals.Self explanatoryLocal vs. globalLocal vs. globalThis is just false.Your network topology might change for some reasonMore like trial and errorCost in resources to serialize/deserialize data and cost in network trafficUse standard technologies. Maybe not relevant for Nservicebus since you must run on windows.
  • http://support.nservicebus.com/customer/portal/articles/861018-overview
  • Services are autonomous – changes on one services should not affect another service through encapsulationContract & schema – don’t share implementation as contract, framework is fine to shareBoundaries – to communicate over boundaries should be an explicit actCompatibility – security, signing etc. is not defined in main code but as policies
  • But do you really need referential integrity? What if you didn’t delete data, and modeled the business lifecycle of data instead?Products no longer for sale, though previous orders can continue processing, inventory liquidated, etc.
  • Consider overriding ConfigureHowToFindSaga to be able to get the correct saga for processing messages
  • Transcript

    • 1. NSERVICEBUSInspired by: The course authored by Udi Dahan Oslo/Fagdag Espen Ekvang/Tomas Jansson 01/03/2013
    • 2. AGENDA 2• Intro• Messaging and queues• Testing• SOA• Saga
    • 3. INTRO 4• Fallacies of distributed computing• Why NServiceBus?• Bus vs. Broker• Service orientation• Excercises
    • 4. FALLACIES OF DISTRIBUTED COMPUTING 51. The network is reliable2. Latency isn’t a problem3. Bandwidth isn’t a problem4. The network is secure5. The topology won’t change6. The administrator will know what to do7. Transport cost isn’t a problem8. The network is homogeneous Cant’ assume WHEN the message will arrive, IF AT ALL
    • 5. WHY NSERVICEBUS 61. The network is reliable2. Latency isn’t a problem NServiceBus addresses the first five directly3. Bandwidth isn’t a problem4. The network is secure5. The topology won’t change6. The administrator will know what to do7. Transport cost isn’t a problem8. The network is homogeneousThe most developer-friendly service bus for SOA on .NET
    • 6. BUS VS. BROKER 7• Bus is not necessarily physically separate• Simpler; no routing or service fail over• No single point of failure App App Buss.dll Broker App App Buss.dll Buss.dll App App
    • 7. TENETS OF SERVICE ORIENTATION 8• Services are autonomous• Share contract & schema, not class or type• Boundaries are explicit• Compatibitility is base on Policy
    • 8. LAYERS & COUPLING 9 Tight coupling Loose coupling Sales Shipping CRM UI BL DAL DB Referential Integrity Reintroduces coupling
    • 9. WHEN CAN I WRITE SOME CODE? 10• Getting started • New class library • Install-Package NServiceBus.Host• Logging • NServiceBus uses log4net, you can configure logging in app.config • Default output is console
    • 10. EXERCISES 11HELLO WORLDLOGGING
    • 11. MESSAGING AND QUEUES 12• Store & forward• Dangers of store & forward• Request/Response• Messaging and NServiceBus• Exercises
    • 12. STORE & FORWARD 13 SERVER MSMQ OUTGOING INCOMING Store & Forward writes to disk Resilient in the face of failures MSMQ OUTGOING INCOMING CLIENT
    • 13. DANGERS OF STORE & FORWARD 14• If target is offline for an extended period of timemessages can fill up the disk • Can cause a server to crash• Especially problematic in B2B integration • 1 MB/message, 100 message/sec = 6GB/minute• Solution – discard messages after a while • Use [TimeToBeReceived("00:01:00")] on the message definition
    • 14. REQUEST/RESPONSE 15 SERVER MSMQ OUTGOING INCOMINGClient can’t assumewhen a response Equivalent to 2will arrive, if at all one-way messages MSMQ OUTGOING INCOMING CLIENT
    • 15. REQUEST/RESPONSE 16• Message is sent from the server to the client’s queue If the client is offline, message sits in the server machine’s outgoing queue• Client is not blocked until response arrives• If two requests were sent, responses may arrive out of order
    • 16. WARNING! THIS IS NOT RPC 17• Do NOT try to implement regular request/response patterns on top of messaging• The client should be designed so that it can continue operating if a response never comesDifferences from RPC• RPC is easy to code • After invoking a web service • Next line of code assumes we’ve got a response• RPC problems • Can’t reason about the time between one line of code and another• Messaging makes this all explicit
    • 17. MESSAGING AND NSERVICEBUS 18 SERVER MSMQ OUTGOING INCOMING Transaction MSMQ OUTGOING INCOMING CLIENT
    • 18. DEFINE A MESSAGE 19• Preferably inherit from IEvent or ICommand• Use IMessage when replying using Bus.Reply()• Also possible to define your own convention • Configure.DefiningMessagesAs(t=>MyOwnConvention(t))• Add properties like a regular class/interface• Keep contract definintions in their own assembly/projectpublic class MyEvent: IEvent {}
    • 19. INSTANTIATE A MESSAGE 20• var myMessage = new MyMessage();• var myMessage = Bus.CreateInstance<MyMessage>();
    • 20. SEND A MESSAGE 21Bus.Send(messageObject);Can instantiate and send together (useful for interfaces):Bus.Send<IMessage>((message) =>{ message.Prop1 = value1; message.Prop2 = value2;});
    • 21. SPECIFY DESTINATION 221. Bus.Send(destination, messages); Requires that application manages routing2. Configure destination for message type. In <UnicastBusConfig>, under <MessageEndpointMappings> specify one of the following: - <add Messages="assembly" Endpoint="destination"/> - <add Messages="type" Endpoint="destination"/>3. Specify destination using - QueueName@ServerName , or - Just QueueName for the same machine
    • 22. HANDLE A MESSAGE 23Write a class that implements IHandleMessages<T> where T is a message typepublic class MyHandler : IHandleMessages<MyMessage>{ public void Handle(MyMessage message) { }}Remember to specify in <UnicastBusConfig>, under<MessageEndpointMappings> one of the following:- <add Messages="assembly" Endpoint="source"/>- <add Messages="type" Endpoint="source"/>
    • 23. CONFIGURING AN ENDPOINT 24When configuring an endpoint inherit from1. Using AsA_Client will - use non-transactional MsmqTransport - purge its queue of messages on startup - processes messages using its own permissions, not those of the message sender2. Using AsA_Server will - use transactional MsmqTransport - not purge its queue of messages on startup, hence fault-tolerant - processes messages using the permissions of the sender (impersonation)3. Using AsA_Publisher will - extends AsA_Server - indicates to the infrastructure that a storage for subscription request is to be set up
    • 24. EXERCISES 25ONE-WAY MESSAGING (CLIENT)PROCESSING MESSAGES (SERVER)EXCEPTIONS
    • 25. UNIT TESTING MESSAGE HANDLERS 26Available from NuGet usingInstall-Package NServiceBus.TestingProvides the ability to set expectations around how message handlers handle messages• Expect: Send, Reply, Publish, etc...Test.Initialize();Test.Handler<MyHandler>() .ExpectPublish<MyMessage>(message => message.Prop1 == value1) .OnMessage<SomeEvent>(someEvent => { someEvent.Prop1 = inputValue1; });
    • 26. EXERCISE 27UNIT TESTING
    • 27. SAGA 28• Definition• Saga declaration• Saga ending• Saga testing• Exercise
    • 28. SAGA - DEFINITION 29A Saga:• Is a pattern for implementing long-lived transaction by using a series of shorter transactions• Holds relevant state to needed to process mulitple messages in a ”saga entity”• Are initiated by a message (event/command)
    • 29. SAGA - DECLARATION 30public class MyPolicy : Saga<MyPolicyData>, IAmStartedByMessages<MyMessage1>, IHandleMessages<MyMessage2>{ public void Handle(MyMessage1 order) public void Handle(MyMessage2 order)}• Methods are like regular message handling logic• Sagas can be started by multiple messages (IAmStartedByMessages<T>)• First messages should start saga, following messages should be processed by the same one
    • 30. SAGA – DECLARATION CONT. 31public class MyPolicyData : ISagaEntity{ public Guid Id { get; set; } public string Originator { get; set; } public string OriginalMessageId { get; set; }}
    • 31. ENDING A SAGA 32MarkAsComplete();• Can call this from any method• Causes the saga to be deleted• Any data that you want retained should be sent on (or published) via a message
    • 32. UNIT TESTING A SAGA 33Test.Saga<MyPolicy>() .ExpectPublish<Message1>(/* check values */) .ExpectSend<Message2>(/* check values */) .ExpectReplyToOriginator<Message3>(/* check values */) .When(saga => saga.Handle(myMessage));/* check values */message => return(message.Data == someValue);
    • 33. EXERCISE - SAGAS ROCK 34
    • 34. EXTRA EXERCISES 35TIMEOUTCUSTOM XML NAMESPACECONFIGURABLE ROUTINGDEPENDENCY INJECTIONWEB-APP HOSTINGFULL DUPLEXDISTRIBUTION GROUP EXERCISE

    ×