Introducing Nimbus - Azure Service Bus made easy

3,918 views
3,861 views

Published on

Introducing Nimbus. Azure Service Bus made easy by Damian Maclennan and Andrew Harcourt

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total views
3,918
On SlideShare
0
From Embeds
0
Number of Embeds
2,519
Actions
Shares
0
Downloads
15
Comments
0
Likes
0
Embeds 0
No embeds

No notes for slide

Introducing Nimbus - Azure Service Bus made easy

  1. 1. Introducing Nimbus – Azure Service Bus made easy Damian Maclennan @damianm Andrew Harcourt @uglybugger 1
  2. 2. Readify Principal Consultants 2
  3. 3. What is a Service Bus anyway ????? 3
  4. 4. 4
  5. 5. Queues 5
  6. 6. Topics and Publish / Subscribe 6
  7. 7. Why use a service bus ? Microservice Architecture 7
  8. 8. ENTERPRISE SERVICE BUS 8
  9. 9. ESB vs Microservice (A totally unbiased view) Microservice ESB Loosely Coupled Orchestrated Independently Scalable Centralised Bottleneck Fault tolerant Single Point of Failure Free $$$$$$ 9
  10. 10. Service Bus Implementations • Azure Service Bus • RabbitMQ • MSMQ (With a little help) • ZeroMQ 10
  11. 11. Azure Service Bus is Bus As A Service 11
  12. 12. BAAS 12
  13. 13. Azure Service Bus is totes AMQP compliant!!!! (for all of your “Open Standards” needs) 13
  14. 14. 14
  15. 15. Azure Service Bus has excellent documentation (with community comments) 15
  16. 16. 16
  17. 17. To TEH CODEZ 17
  18. 18. Azure Service Bus Sample 18
  19. 19. Surely there’s a better way! 19
  20. 20. NServiceBus Handler Example 20
  21. 21. NServiceBus makes us sad for different reasons 21
  22. 22. 22
  23. 23. 23
  24. 24. So we made a thing! 24
  25. 25. Nimbus – Azure Service Bus Made Easy https://github.com/damianmac/nimbus https://twitter.com/NimbusAPI 25
  26. 26. Why we wrote Nimbus and why we think it’s good • Open Source… really • Nice Request / Response model • Simple to configure • Async • Doesn’t tie you to a particular anything • Handles some scenarios that others don’t • Works On Premise too with Windows Service Bus 26
  27. 27. MOAR CODEZ 27
  28. 28. Nimbus Architecture Patterns and Scenarios 28
  29. 29. Command / Consumer SendEmailCommand Application Email Service 29
  30. 30. Command / Competing Consumer Email Service SendEmailCommand Application Email Service Only one of these will get the message. Email Service 30
  31. 31. Publish / Subscribe Logistics Service OrderConfirmedEvent Application Customer Purchase History Service All of these things are interested in this event. Email Service 31
  32. 32. Request / Response CustomerHistoryRequest Application CustomerHistoryResponse Customer Purchase History Service 32
  33. 33. Request / Response Load Balancing Customer Purchase History Service CustomerHistoryRequest Application CustomerHistoryResponse Customer Purchase History Service Only one of these will get the message. Customer Purchase History Service 33
  34. 34. Multicast Request / Response with Timeout Geographic Risk Assessment Service FraudlentCardRequest Failed Attempt Service Application IsThisDodgyResponse All of these have n milliseconds to return an opinion. Usage Rate Service 34
  35. 35. Multicast Request / Response take first Risk Assessment Service FraudlentCardRequest Risk Assessment Service Application We take the response from fastest responder. YesThisIsDodgyResponse Risk Assessment Service 35
  36. 36. Competing Publish / Subscribe Logistics Service OrderConfirmedEvent Application Logistics Service Only one of these instances should react. Logistics Service 36
  37. 37. So what next ? 37
  38. 38. 38
  39. 39. http://www.nuget.org/packages/Nimbus/ 39
  40. 40. Need Help ? Damian Maclennan @damianm Andrew Harcourt @uglybugger 40

×