E N D
1. SOA at Merrill Lynch
Andy Brown
Chief Technology Architect
ML & Co.
2. “SOA” wins most overloaded acronym of 2005 A Framework Architecture
A Platform (e.g. IBM, Tibco)
A Company (e.g. SOA Software)
A way of thinking
Abstraction, Interfaces, Implementations
The next biggest thing!
3. The Evolution of Interoperability OSI – OSI –
4. The information required for a typical Bond trade demonstrates the importance of uniquely and consistently identifying Party, Product, Prices and Organizational information...The information required for a typical Bond trade demonstrates the importance of uniquely and consistently identifying Party, Product, Prices and Organizational information...
5. What is our framework for SOA? Challenge : Scope = Enterprise
6. There are 20,000 active CICS licenses at 14,000 CICS customers.
90% of Fortune 500 customers use CICS.
More than 30 million people in over 90 countries use CICS.
An estimated 300,000 programmers develop CICS applications.
Worldwide 30 billion transactions a day run on CICS, amounting to over 1 trillion dollars in volume.
7. Service Oriented Legacy Architecture (SOLA)aka X4ML
9. What are we doing with SOA Frameworks at ML?Example : GPC Integration Framework
10. How does an SOA approach help ? Process Oriented
Prototyping is extremely fast.
Visual - Simple to “get”
Creates a common language (process/data) for technology and business people.
Incremental
re-uses and orchestrates existing technology services and people creating ROA and speeding time to market.
Standards based
Previous iterations of standards did not interoperate effectively. Web Services have created the common syntax…
Secure
Security can be enforced via policy, and can be added by the platform to legacy apps.
11. We are using SOA Platforms to simplify, automate and instrument business process.
12. What are the new problems? Capacity Management and SLAs
Understanding dependencies (and constraints) on underlying services = Process level capacity management.
Getting Integration right
Exposing the right services into catalogs and libraries. Integration can happen at any level from RPC upwards, so we need to advertise services we want people to use.
Security and Privacy
In a complex regulated environment ensuring that policy is enforced across the SOA becomes a level of complexity on top of process definitions and dependencies.
Data
Process integration requires that data issues be addressed. This requires that Semantics and Syntax are agreed at the process/sub-process level. This is a new dialog.
Managing Implementations
The SOA Platforms are very flexible, but without controls this can create poor implementations. Putting real architects to work inside implementation teams is essential.
Skills Gap – Business Process Modeling & Re-engineering
Finding / Training Business/Technology Hybrids who can talk business process and work with architects to define technology implementations. An “uber” Business Analyst
13. Summary – Key takeaways
SOA is here to stay.
SOA creates ROA via systematic reuse.
SOA drives ROI via time to market.
SOA requires Enterprise Architecture
SOA requires retooling & training
14. The End
Andy Brown
Chief Technology Architect