Recommandé
Contenu connexe
Dernier
Dernier (20)
En vedette
En vedette (20)
Reliable integrations with NServiceBus
- 1. Reliable integrations with NServiceBus Andreas Öhlund Enterprise Development Expert
- 2. Agenda • War story • Dragons and how to manage them • A “saga” with a happy ending • Q &A
- 9. Fact: A trip to dragon territory can take a while...
- 10. The usual way public void Handle(OrderPlaced message) { var order = new Order{ Id = message.OrderID }; order.TrackingCode = fedex.BookPickup(order); order.Status = ShippingStatus.PickupBooked; repository.Save(order); }
- 11. The usual way public void Handle(OrderPlaced message) { var order = new Order{ Id = message.OrderID }; 2: order.TrackingCode = fedex.BookPickup(order); 3: order.Status = ShippingStatus.PickupBooked; repository.Save(order); }
- 12. The usual way public void Handle(OrderPlaced message) { var order = new Order{ Id = message.OrderID }; 2: order.TrackingCode = fedex.BookPickup(order); This might take a while! 3: order.Status = ShippingStatus.PickupBooked; repository.Save(order); }
- 14. Database rollback Order Ship TX Store DB
- 15. Database rollback Order Ship TX Store DB
- 16. Database rollback Order Ship TX Store DB
- 17. Database rollback Order No TX Support Ship TX Store DB
- 18. Database rollback Did we just loose an order? Order No TX Support Ship TX Store DB
- 19. Database rollback Order No TX Support Ship TX Store DB
- 20. Database rollback Order No TX Support Ship Order Http TX Store DB
- 21. Design guideline “Interact with non transactional resources using separate endpoints”
- 22. R# Extract endpoint public void Handle(OrderPlaced message) { repository.Save(new Order { Id = message.OrderID, Status = ShippingStatus.AwaitingShipment }); bus.Send<BookShipment>(m => { m.OrderID = message.OrderID; }); }
- 23. R# Extract endpoint public void Handle(OrderPlaced message) { repository.Save(new Order { Id = message.OrderID, Status = ShippingStatus.AwaitingShipment }); bus.Send<BookShipment>(m => { m.OrderID = message.OrderID; }); }
- 24. R# Extract endpoint public void Handle(OrderPlaced message) { repository.Save(new Order { Id = message.OrderID, Status = ShippingStatus.AwaitingShipment }); bus.Send<BookShipment>(m => { m.OrderID = message.OrderID; }); }
- 25. R# Extract endpoint public void Handle(ShipmentBooked message) { var order = repository.Get<Order>(message.OrderID); order.TrackingCode = message.TrackingCode; repository.Save(order); }
- 26. Consistency across rollbacks Order TX
- 27. Consistency across rollbacks Order Store DB TX
- 28. Consistency across rollbacks Order Store DB TX Book shipment MQ
- 29. Consistency across rollbacks Order Store DB TX Book shipment MQ
- 30. Consistency across rollbacks Order Store DB TX Book shipment MQ
- 31. Consistency across rollbacks Order Store DB TX Book shipment MQ
- 32. Fact: Not everyone will make it back. Not all return from a trip to the dragons
- 33. What happens if the response is lost? BookShipment Fedex.Ship TX
- 34. What happens if the response is lost? BookShipment Fedex.Ship TimeoutException TX
- 35. What happens if the response is lost? BookShipment Fedex.Ship TimeoutException TX
- 36. What happens if the response is lost? BookShipment Fedex.Ship Commit TimeoutException TX
- 37. Idempotency BookShipment Integration Endpoint
- 38. Idempotency BookShipment http://fedex.com/ship ?id=xyz123 Integration Endpoint
- 39. Idempotency BookShipment http://fedex.com/ship ?id=xyz123 Commit Integration Endpoint
- 40. Idempotency BookShipment http://fedex.com/ship ?id=xyz123 Commit TimeoutException X Integration Endpoint
- 41. Idempotency BookShipment http://fedex.com/ship ?id=xyz123 Commit TimeoutException X Integration Endpoint http://fedex.com/ship ?id=xyz123
- 42. Idempotency BookShipment http://fedex.com/ship ?id=xyz123 Commit TimeoutException X Integration Endpoint http://fedex.com/ship ?id=xyz123 Discard
- 43. Idempotency BookShipment http://fedex.com/ship ?id=xyz123 Commit TimeoutException X Integration Endpoint http://fedex.com/ship ?id=xyz123 Discard
- 44. Idempotency BookShipment http://fedex.com/ship ?id=xyz123 Commit TimeoutException X Integration Endpoint http://fedex.com/ship ?id=xyz123 ShipmentBooked Discard
- 45. Fact: A trip to the dragons may be costly.
- 46. Timeouts vNext • Thread.Sleep is not a good solution • Need a way to have durable timeouts • The NServiceBus timeout manager solves this for us
- 47. Fact: Dragons have home turf advantage.
- 48. Scalable integrations Use throttling to: • Manage traffic peaks • Allow you to control the pace
- 49. A more scalable design Client Server
- 50. A more scalable design Request Client Server
- 51. A more scalable design Request Send Client Server
- 52. A more scalable design Request Send Ticket - come back in T http://fedex.com/responses/xyz123 Client Server
- 53. A more scalable design Request Send Ticket - come back in T http://fedex.com/responses/xyz123 Client Server Recv Cache
- 54. A more scalable design Request Send Ticket - come back in T } http://fedex.com/responses/xyz123 Client T Server http://fedex.com/responses/xyz123 Recv Cache
- 55. A more scalable design Request Send Ticket - come back in T } http://fedex.com/responses/xyz123 Client T Server http://fedex.com/responses/xyz123 Recv Response / come back in T2 Cache
- 56. A more scalable design Request Send Ticket - come back in T } http://fedex.com/responses/xyz123 Client T Server http://fedex.com/responses/xyz123 Recv Response / come back in T2 Cache
- 57. A more scalable design Request Send Ticket - come back in T } http://fedex.com/responses/xyz123 Client T Server http://fedex.com/responses/xyz123 Recv Response / come back in T2 Cache
- 58. Using sagas to control BookShipment message flow Integration Fedex Timeout Fedex Saga Endpoint Manager
- 59. Using sagas to control BookShipment message flow Get ticket Integration Fedex Timeout Fedex Saga Endpoint Manager
- 60. Using sagas to control BookShipment message flow Get ticket Integration Fedex Timeout Fedex Saga Endpoint Manager
- 61. Using sagas to control BookShipment message flow Get ticket Integration Fedex Timeout Fedex Saga Endpoint Manager
- 62. Using sagas to control BookShipment message flow Get ticket Wake me up in T Integration Fedex Timeout Fedex Saga Endpoint Manager
- 63. Using sagas to control BookShipment message flow Get ticket Wake me up in T Integration Fedex Timeout Fedex Saga Endpoint Manager
- 64. Using sagas to control BookShipment message flow Get ticket Wake me up in T Integration Fedex Timeout Fedex Saga Endpoint Manager Get Data
- 65. Using sagas to control BookShipment message flow Get ticket Wake me up in T Integration Fedex Timeout Fedex Saga Endpoint Manager Get Data
- 66. Using sagas to control BookShipment message flow Get ticket Wake me up in T Integration Fedex Timeout Fedex Saga Endpoint Manager Get Data
- 67. Code...
- 70. Thanks for listening! Andreas Öhlund Enterprise Development Expert
Notes de l'éditeur
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- Fallacies of distributed computing\n
- Good DDD but still dangerous\nWorks well in test, but takes a long time in production\nKeeps the transactions open longer (other handlers can have opened the db connection\nFallacy: Latency is zero\n
- Good DDD but still dangerous\nWorks well in test, but takes a long time in production\nKeeps the transactions open longer (other handlers can have opened the db connection\nFallacy: Latency is zero\n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- \n
- Find a way to break up the process\nIntroducing a new status\n
- Find a way to break up the process\nIntroducing a new status\n
- \n
- Consistent processing of orders\n
- Consistent processing of orders\n
- Consistent processing of orders\n
- Consistent processing of orders\n
- Consistent processing of orders\n
- \n
- Fallacy: the network is reliable\nRetries might cause problems\nNot idempotent\n \n\n
- Fallacy: the network is reliable\nRetries might cause problems\nNot idempotent\n \n\n
- Fallacy: the network is reliable\nRetries might cause problems\nNot idempotent\n \n\n
- Requires collaboration with the other party\nNServiceBus preserves message ids even across the error queue\n\n
- Requires collaboration with the other party\nNServiceBus preserves message ids even across the error queue\n\n
- Requires collaboration with the other party\nNServiceBus preserves message ids even across the error queue\n\n
- Requires collaboration with the other party\nNServiceBus preserves message ids even across the error queue\n\n
- Requires collaboration with the other party\nNServiceBus preserves message ids even across the error queue\n\n
- Requires collaboration with the other party\nNServiceBus preserves message ids even across the error queue\n\n
- Requires collaboration with the other party\nNServiceBus preserves message ids even across the error queue\n\n
- Partner might charge per call\nOn a device with limited battery or where traffic cost might be high\n
- \n
- Sleep locks up threads, bad for throughput\nSleep doesn&#x2019;t survive restarts\nMessage based alarm clock\n
- You play according to their rules\nDragons need to control the pace of the raiding parties\nMust do throttling to be scalable\nImpossible to maintain SLA&#x2019;s otherwise\n
- \n
- The \n
- The \n
- The \n
- \n
- Msmq.Send is very quick, 7000msg/s given no DTC\nAdjust T to tune the load\nResponses can be served of different servers\nCQRS\nCallback protocol can be used if the number of clients are small (REST / HTTP)\n
- Msmq.Send is very quick, 7000msg/s given no DTC\nAdjust T to tune the load\nResponses can be served of different servers\nCQRS\nCallback protocol can be used if the number of clients are small (REST / HTTP)\n
- Msmq.Send is very quick, 7000msg/s given no DTC\nAdjust T to tune the load\nResponses can be served of different servers\nCQRS\nCallback protocol can be used if the number of clients are small (REST / HTTP)\n
- Msmq.Send is very quick, 7000msg/s given no DTC\nAdjust T to tune the load\nResponses can be served of different servers\nCQRS\nCallback protocol can be used if the number of clients are small (REST / HTTP)\n
- Msmq.Send is very quick, 7000msg/s given no DTC\nAdjust T to tune the load\nResponses can be served of different servers\nCQRS\nCallback protocol can be used if the number of clients are small (REST / HTTP)\n
- Msmq.Send is very quick, 7000msg/s given no DTC\nAdjust T to tune the load\nResponses can be served of different servers\nCQRS\nCallback protocol can be used if the number of clients are small (REST / HTTP)\n
- Msmq.Send is very quick, 7000msg/s given no DTC\nAdjust T to tune the load\nResponses can be served of different servers\nCQRS\nCallback protocol can be used if the number of clients are small (REST / HTTP)\n
- Msmq.Send is very quick, 7000msg/s given no DTC\nAdjust T to tune the load\nResponses can be served of different servers\nCQRS\nCallback protocol can be used if the number of clients are small (REST / HTTP)\n
- Picture == the essence of sagas\n * Only control logic\n\n
- Picture == the essence of sagas\n * Only control logic\n\n
- Picture == the essence of sagas\n * Only control logic\n\n
- Picture == the essence of sagas\n * Only control logic\n\n
- Picture == the essence of sagas\n * Only control logic\n\n
- Picture == the essence of sagas\n * Only control logic\n\n
- Picture == the essence of sagas\n * Only control logic\n\n
- Picture == the essence of sagas\n * Only control logic\n\n
- \n
- \n
- \n
- If we learn to manage our dragons they can be of great use\nTell the story on how we built our own queuing system\n\n
- If we learn to manage our dragons they can be of great use\nTell the story on how we built our own queuing system\n\n