The road to a Service Oriented Architecture is paved with messages
Download as PPTX, PDF0 likes101 views
The document discusses the importance of messaging in service-oriented architecture (SOA), emphasizing that transactions across service boundaries can be complex due to the need for atomic operations. It outlines various messaging patterns, highlighting the benefits of reduced coupling, asynchronous communication, and easier maintenance. The document advocates for using messages as a way to facilitate interactions while managing errors and ensuring delivery within autonomous components.
The road to a Service Oriented Architecture is paved with messages
- 1. The road to a Service Oriented Architecture is paved with messages
- 2. All I want to do when I wake up in the morning is… (cit. Rosanna, Toto, Toto IV)
- 3. Tickets web site Buy a ticket Stage dive… :-)
- 4. All what they want to do is…
- 5. Display available tickets Reserve with the theater Charge my credit card Deal with insurance Ship tickets Deal with their stuff
- 6. sometimes order doesn’t matter… sometimes it does!
- 7. spot the
- 10. Transaction boundaries • user perspective: single operation • system perspective: multiple operations • That should be “atomic” (not as in ACID) • The business transaction spans multiple boundaries • Theater reservation • Credit card • Insurance • Shipping • Internal stuff • and more…
- 11. …big ball of mud… When crossing service boundaries we cannot expect transactions to work SOA Boundaries are explicit
- 12. DTC forget you must Compensation you should welcome Idempotency your best friend is
- 13. Messages you want Messages are Atomic Messages are Unique Messages tell stories
- 14. Messaging Patterns Because not all communication is born equal
- 15. Request/Response message sent to someone implies some coupling we know each other
- 16. Pub/Sub broadcasted event, in the past implies less coupling subscribers know the publisher
- 17. FinanceMarketing OrdersCheckout request Shipping Charge card request Payment Gateway Charge card response Warehouse Collect Items Order Submitted Shipping Order shipped others Order Payed Shipment request FedEx Gateway Shipment response Collection Completed
- 18. Charge card request Payment Gateway Shipping FinanceMarketing OrdersCheckout request Shipping Warehouse Collect Items Collection Completed Order Submitted Payment Failure We won’t ship! :-)
- 19. Messages in a nutshell • Less coupling • respect your boundaries • No temporal coupling • messages are asynchronous • Much less maintenance/deployment headaches • autonomous components • Easy scale-out • competing consumers • Guaranteed delivery • with error management
- 20. We do this all day long Mauro Servienti Solution Architect @ Particular Software makers of NServiceBus mauro.servienti@particular.net @mauroservienti //blogs.ugidotnet.org/topics //milestone.topics.it
- 21. Thank you Go! Tell stories about your world.
Editor's Notes
- #7: Let me tell that you of that time when {the vendor I cannot name} gifted me with a nice {flat x86 device with a very thin keyboard} {the story} It’s obvious that there are two very different point of views here.
- #10: The ticket is one, from our point of of view is a ticket. From the point of view of Customer Care a ticket is something completely different to what it is from the point of view of someone else
- #14: As in a ledger or a bank account statement