One of the options on the table when implementing a Service Oriented Architecture (SOA), or the communication style across multiple microservices, is based on messages and a service bus. This talk will drive you through the basic SOA building blocks, introduce message based architectures, and will connect the dots between technology and architectural principles through some samples using NServiceBus.
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
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
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.
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