Making communications across boundaries simple with NServiceBus
Download as PPTX, PDF3 likes712 views
The document covers the setup and use of NServiceBus and Azure Service Bus for secure and reliable communication between software components across various environments. It provides insights into endpoint management, message handling, topology types, transaction modes, and performance considerations. It also discusses configurations for efficient message exchange, including batching and delivery strategies, along with the advantages and disadvantages of different topologies.
![Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus
Poisonous messages are
dead lettered w/o retries
Messages with number of
immediate retries bigger than
entity`s delivery will dead
letter.
Poisonous & dead-lettered messages
Example:
Immediate retries set to X
Entity`s DeliveryCount set to X-1
Unsupported Transport
encoding (i.e. not stream or
byte[])](https://image.slidesharecdn.com/asbnsb-161215174304/85/Making-communications-across-boundaries-simple-with-NServiceBus-29-320.jpg)
Making communications across boundaries simple with NServiceBus
- 1. Yves Goeleven & Sean Feldman Solution Architects & Azure MVPs http://particular.net Azure Service Bus & NServiceBus Setting up communication across boundaries
- 2. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Secure & reliable communication between software components across network boundaries. • Inside cloud services • Between datacenters • Between branch offices • Hybrid solutions • IoT & Mobile devices When do you need Azure Service Bus ?
- 3. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Framework to simplify the development of distributed business and workflow applications. • .NET native workflow & pub/sub • Simplicity, reliability, scalability and performance • Runs on premises, in the cloud, or either • Supports a wide range of messaging transports, deals with transport technology complexity What is NServiceBus for? Endpoint Endpoint Transport Azure Service Bus RabbitMQ MSMQSQL Server ASQ SQS …
- 4. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus An Endpoint is a logical entity that communicates with other Endpoints via messaging. Endpoint typically equates to a process. Each Endpoint • Has an identifying name • Contains a collection of Message Handlers and Sagas • Can be deployed to a number of machines and environments (instances) NServiceBus – simple overview Endpoint Endpoint Transport class PlaceOrder : ICommand { public Guid Id { get; set; } public string Product { get; set; } } instance.Send(new PlaceOrder()) class Handler : IHandleMessages<PlaceOrder> { Task Handle(PlaceOrder message) { // your code here } }
- 6. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Transport => MessagePump + Dispatcher ( + additional features) Forked pipeline of behaviors (handler returns) Some behaviors might invoke transactional resources like Persisters Startup infrastructure (TransportDefinition, Feature, Installer, ...) NServiceBus - endpoint internals MessagePump Dispatcher Handler Startup Infrastructure
- 7. Connectivity
- 8. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Installer called at startup TopologyCreator inquires Topology for what needs to be created • For each entity in the topology constructs creator object Which in turn uses namespace manager to create entities • deals with all possible exceptions Creation Installer Topology TopologyCreator Namespace Manager Queue, Topic & Subscription Creators SubscriptionManager
- 9. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus MessagePump & Dispatched inquire Topology to know what to receive from/send to Pools of receivers, senders & factories (default poolsize = #cores) Active lifecycle management (connection reestablished on drop) Circuit breaker pattern Connectivity Management MessagePump Dispatcher Pool of receivers Pool of senders Pool of factories SBMP over TCP SBMP over TCP Context LifecycleManager LifecycleManager LifecycleManager Circuit breaker Topology
- 10. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Represents the layout of service bus entities that allow endpoints to communicate. • Explicit concept in transport so that it can be swapped. • ASB’s forwarding feature provides near endless possibilities. What is a topology? Forwarding Endpoint C Endpoint A Endpoint B Topology
- 11. Let’s have a look at some topologies
- 12. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Entity usage • Commands vs Events • Embed message types (f.e. filters, entity names) • Does each namespace type support the entities used • Native capabilities Ownership • Endpoints may not be aware of the full topology • Awareness creates coupling, do you want that? • Some entities may not belong to any endpoint Performance impact (Backwards) compatability Multiple namespaces, Partitioning, HA • No forwarding between namespaces Things to consider for a topology
- 13. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Each endpoint has its own input queue Sends direct to input queue, does not leverage pub/sub capabilities of ASB, instead uses storage driven publishing from NSB Basic topology Endpoint C Endpoint B Endpoint A Sphere of ownership
- 14. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Basic topology: pros and cons Pros Cons Simple mode No native pub/sub Can leverage any messaging namespace type (Basic, standard, premium) Publisher coupled to subscriber (in both directions) Easy to port from MSMQ External dependency on storage Integrates with auto-scale No native auditing on commands/events
- 15. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Each endpoint has its own input queue & topic Sends direct to input queue, publish via topic Endpoint oriented topology Endpoint C Endpoint B Endpoint A EndpointC.TypeA EndpointB.TypeA EndpointB.TypeB EndpointA.Events
- 16. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Endpoint oriented topology: pros and cons Pros Cons Publisher decoupled from subscribers Subscribers coupled to Publishers No dependency on storage Hard to use polymorphic events Cannot handle changes in event hierarchy Possible event overflow Integrates with auto-scale Auto-scale for input queue only Can not leverage basic namespace Native auditing on events Native auditing on events very hard No native auditing on commands
- 17. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Each endpoint has its own input queue, shared topics for publishing Sends direct to input queue, publish via topic Forwarding topology Endpoint C Endpoint B Endpoint A Type A Type A Type B EndpointB EndpointC Bundle-1
- 18. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Forwarding topology: pros and cons Pros Cons No dependency on storage Can not leverage basic namespace No coupling between publisher & subscriber No native auditing on commands Supports polymorphism Change in message hierarchy is transparent Integrates with auto-scale Protected against overflow Native auditing on events
- 19. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Each endpoint has its own input topic, shared topics for publishing Sends direct to input topic, publish via topic “Topic all the things” topology Endpoint C Endpoint B Endpoint A Type A Type A Type B Bundle-1 EndpointB EndpointC
- 20. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus “Topic all the things” topology: pros and cons Pros Cons No dependency on storage Can not leverage basic namespace No coupling between publisher & subscriber Does not integrate with auto-scale Supports polymorphism Change in message hierarchy is transparent Protected against overflow Native auditing on commands & events
- 22. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus 1. Unreliable – TXs disabled 2. Receive Only – transport TXs 3. Sends atomic with Receive 4. Transaction Scope – Distributed TXs NSB Transaction Modes
- 23. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus ReceiveAndDelete receive mode Not recommended as when failures occur, messages will be permanently lost. Use case: telemetry Transaction Mode: Unreliable Endpoint Receive And Delete Delete
- 24. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus PeekLock receive mode Partial results - Updates to data stores - Message sends Higher performance HA – multiple namespaces Transaction Mode: Receive Only Endpoint DLQ Temporal Lock Delete
- 25. Endpoint Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus PeekLock receive mode + transaction + send via No ghost messages BUT, data is not included in transport transaction (data should have its own transaction) Transaction Mode: Sends atomic with Receive Message Receiver DLQ Temporal Lock Delete Message Sender
- 26. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Send via requires transaction scope That scope does not allow other transactional resources inside it Requires strategic suppress scopes in the pipeline to work Transaction Mode: Sends atomic with Receive MessagePump Dispatcher Handler Via scope wraps pipeline invocation Suppress scope wraps Handler scope Connections enlists in Handler scope Enlists in Via scope Connections must be wrapped in suppress scope
- 27. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus DTC is not supported by ASB Transaction Mode: Transaction Scope
- 28. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus - Successfully processed messages go to Audit queue - Recoverability for failed messages - Immediate retries - Delayed retries Messages failed all retries go to Error queue Total Number of Attempts Business errors (ImmediateRetries:NumberOfRetries + 1) x (DelayedRetries:NumberOfRetries + 1)
- 29. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Poisonous messages are dead lettered w/o retries Messages with number of immediate retries bigger than entity`s delivery will dead letter. Poisonous & dead-lettered messages Example: Immediate retries set to X Entity`s DeliveryCount set to X-1 Unsupported Transport encoding (i.e. not stream or byte[])
- 31. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Default dispatch mode: batched Dispatch Mode Endpoint A Endpoint B Namespace Batch Endpoint A Endpoint B Namespace Batch Optional (explicit): immediate 1 2
- 32. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Each namespace is sent separately Dispatching to multiple namespaces Endpoint B Namespace 1 Endpoint C Namespace 2 Batch Batch Endpoint A Batch
- 33. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Batch size is estimated using padding percentage. Default padding: 5%. Calculated message size = Raw body size + Custom headers size (keys + values) + Standard properties estimated size + padding % Batch Size Body Size Custom Headers (keys + values) Standard Properties (estimated) Padding % Body Size Custom Headers (keys + values) Standard Properties (estimated) Padding % … Body Size Custom Headers (keys + values) Standard Properties (estimated) Padding % Body Size Custom Headers (keys + values) Standard Properties (estimated) Padding % … Up to MAX_SIZE or 100 messages …
- 34. Introduction to ServiceInsight for NServiceBusNServiceBus & Azure Service Bus Defaults & what needs to be considered if really high perf is required • Awaiting for combined Tasks vs individual tasks • Number of Factories and clients, concurrency, prefetch Performance Tuning
- 36. Thank you
- 37. Q&A