Recomendados
Más contenido relacionado
La actualidad más candente
La actualidad más candente (15)
Similar a Introducing Nimbus - Azure Service Bus made easy
Similar a Introducing Nimbus - Azure Service Bus made easy (20)
Último
Último (20)
Introducing Nimbus - Azure Service Bus made easy
- 1. Introducing Nimbus – Azure Service Bus made easy Damian Maclennan @damianm Andrew Harcourt @uglybugger 1
- 3. What is a Service Bus anyway ????? 3
- 4. 4
- 5. Queues 5
- 6. Topics and Publish / Subscribe 6
- 7. Why use a service bus ? Microservice Architecture 7
- 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. Service Bus Implementations • Azure Service Bus • RabbitMQ • MSMQ (With a little help) • ZeroMQ 10
- 11. Azure Service Bus is Bus As A Service 11
- 12. BAAS 12
- 13. Azure Service Bus is totes AMQP compliant!!!! (for all of your “Open Standards” needs) 13
- 14. 14
- 15. Azure Service Bus has excellent documentation (with community comments) 15
- 16. 16
- 17. To TEH CODEZ 17
- 18. Azure Service Bus Sample 18
- 19. Surely there’s a better way! 19
- 21. NServiceBus makes us sad for different reasons 21
- 22. 22
- 23. 23
- 24. So we made a thing! 24
- 25. Nimbus – Azure Service Bus Made Easy https://github.com/damianmac/nimbus https://twitter.com/NimbusAPI 25
- 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. MOAR CODEZ 27
- 28. Nimbus Architecture Patterns and Scenarios 28
- 30. Command / Competing Consumer Email Service SendEmailCommand Application Email Service Only one of these will get the message. Email Service 30
- 31. Publish / Subscribe Logistics Service OrderConfirmedEvent Application Customer Purchase History Service All of these things are interested in this event. Email Service 31
- 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. 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. 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. Competing Publish / Subscribe Logistics Service OrderConfirmedEvent Application Logistics Service Only one of these instances should react. Logistics Service 36
- 37. So what next ? 37
- 38. 38
- 40. Need Help ? Damian Maclennan @damianm Andrew Harcourt @uglybugger 40