Reply S.p.A. · MIL:REY
Reply — Technical Presentation (November 2022)
20 slides from Reply's technical presentation, November 2022
Slide 1: SOA – everyone focuses on re-use but nobody seems to worry about re-work!
“SOA – everyone focuses on re-use but nobody seems to worry about re-work!” SOA Strategy
Slide 2: Scope statement
Scope statement • One of the key promises of SOA is re-use, and over time organisations are increasingly becoming successful in achieving that goal; However… • There are external factors that also have an equal bearing on the success of an SOA implementation. • Factors such as changing standards and
Slide 3: Focus
Focus • This session discusses change • Changing face of standards • Maturing of technologies • How to minimise impact of change on design and implementation of SOA • Approaches • Techniques • Methods • Focus is primarily around integration and implementation technologies 3
Slide 4: SOA technology problem
SOA technology problem • You cannot rely on the technologies still being around in their current form in 5 years time • Solutions will reach an end-of-life • If an implementation is tightly bound in to the technology it is going to require re-work • The business case around re-use may no longer stac
Slide 5: Some examples…
Some examples… • Activesoft • eGate • Activeworks/Broker • InConcert • Crossworlds/ICS • Tuxedo • Partner Agreement Manager • eLink • WMQ Workflow • Business Connector • InterConnect 5
Slide 6: Even standards are changing
Even standards are changing • Supporting standards are also changing • Be it ws-* standards maturing • Best practice/proprietary standards • E.g. WSDL, BPEL, REST, ws-security, SCA… • Messaging standards are also changing • Change in paradigm between versions of messaging standards • Data & informat
Slide 7: Methods & approaches have changed too
Methods & approaches have changed too • SCRUM • RAD • ITIL • COBIT • TOGAF 7
Slide 8: Impact on business benefit
Impact on business benefit • Re-work in line with technology lifecycle • Potential vendor technology lock-in or proprietary upgrade path • Ongoing re-training to support technologies and standards • Diminished ROI over time • Not master of own business benefit destiny 8
Slide 9: Solutions
“SOA – everyone focuses on re-use Solutions but nobody seems to worry about re-work!” Solutions
Slide 10: Don’t just take the technology out of the box
Don’t just take the technology out of the box • Prescribed vendor implementation MAY lead you down a road of vendor dependency… • SOA technologies should be considered as assembly kits providing… Components Tools • What matters is how you use them…Define your own assembly instructions. 10
Slide 11: Plan & architect first, implement later
Plan & architect first, implement later • Plan the strategy & define the architecture of the solution domain first • Define it at a logical level of abstraction • Preferably define a complete logical semantic layer • Do not bind the architecture in to the way the physical tool would lead you to do t
Slide 12: Avoid incorporating proprietary products & standards into your architecture solution
Avoid incorporating proprietary products & standards into your architecture solution • Common mistakes in SOA implementations include: − Physical technology as logical solution − Coding by tool e.g. ESQL, Monk, etc. − Binding communication & transformation together − …or indeed binding transformatio
Slide 13: Key goals
Key goals • Define services agnostic of their implementation − Provide logical view of services • Model the services to be implemented logically and map them against logical components implementing that service − Avoid defining a service specific to a particular technology • Utilise open standards −
Slide 14: Consider interoperability between standards
Consider interoperability between standards • Define an interoperable set of standards for internal use − Communication − Messaging − Data − Access − Services − Processes 14
Slide 15: Do not confuse internal with B2B/B2C requirements
Do not confuse internal with B2B/B2C requirements • Insulate internal integration from external change − Deal with external standards as a boundary issue − Do not attempt to embed what is done for partners for internal use • What is required to do business with partners and consumers is not the same
Slide 16: Break down the problem into its constituent parts
Break down the problem into its constituent parts • Achieving business agility will be constrained by brittle & tightly coupled technology solutions − Not only should services be loosely coupled, − BUT architecture components should be loosely coupled also • Don’t mix transformation with message sen
Slide 17: Multi-vendor, multi-technology support
Multi-vendor, multi-technology support Be pragmatic, architect for a heterogeneous Physical view provides a environment detailed relationship between the Logical (technology neutral) view of the To-Be SOA Architecture and your chosen technology platform(s) Conceptual & Logical views provide a techno
Slide 18: Architect for end-of-life
Architect for end-of-life You know it will happen so architect for it from the outset Architect a decoupling layer for end-of-life from the outset …Then different paradigms can interoperate ? + + Future Now Legacy 18
Slide 19: Thoughts to take away
Thoughts to take away • Architect the SOA infrastructure − At a logical level of abstraction − Break down the problem into clearly demarcated tasks − Utilise selected interoperable standards − Don’t bind in preferred physical technology specific implementation detail • The way in which services are
Slide 20: Contacts
Contacts www.replyltd.co.uk