240 likes | 354 Views
Waiting for SOA (was Enterprise Web Integration Using .NET 3.5). Ian Robinson, ThoughtWorks http:// iansrobinson.com /. Two worlds. Mature SOA discourse BUT - Many organisations remain inexperienced in SOA Gentrification. Beckett’s dilemma. Competing forces
E N D
Waiting for SOA (was Enterprise Web Integration Using .NET 3.5) Ian Robinson, ThoughtWorks http://iansrobinson.com/
Two worlds • Mature SOA discourse • BUT - Many organisations remain inexperienced in SOA • Gentrification
Beckett’s dilemma • Competing forces • Seemingly overwhelming size and complexity • “You must go on, I can't go on, I'll go on”
Case study: Midstream oil and gas company • Connect upstream producers with downstream refiners • Frequent touch: • Haulage • Blending • Asphalt • Synergies between services • Acquisitive • 50+ significant systems • Approx half vendor/package, half custom
The challenges • Lack of business process agility • Implications of database replication architecture
Initial engagement • Developing a service-oriented competency • Composition of well-understood, simple techniques
Goals • Make early interventions • Learning what to defer
Workshops overview • Collaborative: business and IT stakeholders • Sample significant business processes: • Production movement • Customer exposure • Shipping services • New employee hired
Back to basics: Entities, actors and actions Production,Diluent, Truck, Terminal Dispatcher, Driver, Operator Dispatching, Hauling, Analyzing, Blending
Production states and events Pickup Connect Blend Awaiting haul Being hauled In storage Blended Crude connected to terminal Diluent connected to terminal Lab analysis available
Existing replication strategy Existing Applications Existing Applications ?
Relieving the replication burden Logistics Operations Existing Applications Existing Applications
Increasing process agility Logistics Operations Existing Applications Existing Applications Lab Analysis Existing Applications Shipper Services
Services • Host for one or more business functions • Useful only insofar as they are consumed • Business-meaningful events will continue to occur no matter the systems that come and go
Integration • Bad integration • Good integration
Workshop observations • Sequential workflows quickly become overly complex • Folk IT • Tolerate a moment of crisis
Conclusions • Look for business-meaningful behaviours and events • Identify service consumer expectations • Iterate over business process descriptions • Encourage wide-ranging ownership of a service-oriented competency