Skip to main content
UploadLanguage (EN)Support
BusinessMobileSocial MediaMarketingTechnologyArt & PhotosCareerDesignEducationPresentations & Public SpeakingGovernment & NonprofitHealthcareInternetLawLeadership & ManagementAutomotiveEngineeringSoftwareRecruiting & HRRetailSalesServicesScienceSmall Business & EntrepreneurshipFoodEnvironmentEconomy & FinanceData & AnalyticsInvestor RelationsSportsSpiritualNews & PoliticsTravelSelf ImprovementReal EstateEntertainment & HumorHealth & MedicineDevices & HardwareLifestyle
Mauro Servienti, profile picture
Uploaded byMauro Servienti
PPTX, PDF909 views

THE ROAD TO A SERVICE ORIENTED ARCHITECTURE (SOA)

The document discusses the implementation of a service-oriented architecture (SOA) using a message-based infrastructure to enhance ticketing systems. It emphasizes the importance of addressing transaction boundaries and suggests using messaging patterns to minimize coupling between services, leading to better scalability and error management. The author advocates for the use of asynchronous, atomic messages to facilitate seamless operations across multiple components.

Software◦
Downloaded 11 times
The road to a Service Oriented Architecture is paved with a message based infrastructure
Mauro Servienti Solution Architect @ Particular Software, makers of NServiceBus mauro.servienti@particular.net @mauroservienti
All I want to do when I wake up in the morning is… (cit. Rosanna, Toto, Toto IV)
Tickets web site Buy a ticket Stage dive… :-)
All what they want to do is…
Display available tickets Reserve with the theater Charge my credit card Deal with insurance Ship tickets Deal with their stuff
Sometimes order is important… Sometimes not
spot the
Multiple resources -- Multiple owners
Transaction boundaries • user perspective: single operation • ticketing system perspective: multiple operations • That should be “atomic” • The business TX crosses multiple boundaries • Theater reservation • Credit card • Insurance • Shipping • Internal stuff • End we’ll end up in a…
…big ball of mud… When crossing service boundaries we cannot expect transactions to work SOA Boundaries are explicit
DTC forget you must Compensation you should welcome Idempotency your best friend is
Messages you want Messages are Atomic Messages are Unique Easily implements Ledger semantic
Messaging Patterns Because not all communication is born equal
Request/Response message sent to someone implies some coupling we know each other
Pub/Sub broadcasted event, in the past implies less coupling subscribers know the publisher
Tickets reservation service Tickets reservation service Order management service Order management service Tickets reservation service Credit Card service Marketing service Other stuff Buy ticket Charge Card Ticket reserved Reserve Tickets
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
Do you want more? Free e-book available at: http://go.particular.net/cloudconfE
Thank you Go! SOA-fy your world