Ashish Pradhan - Legacy Systems & SOA - Interop Mumbai 2009


Published on

Historically, the ROI for SOA has been measured based on the quick ‘time to market’ and the ‘reuse of assets’ that it provides. This session presents a fresh perspective on Legacy Systems, as an extreme case of SOA, and attempts to show enterprises how by merely identifying (not creating) the right envelope around the existing legacy-assets, the dream and benefits of SOA can easily be achieved by the business.

Published in: Technology, Business
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide

Ashish Pradhan - Legacy Systems & SOA - Interop Mumbai 2009

  1. 1. LEGACY SYSTEMS & SOA (If you have a Legacy System, your journey to SOA is half-complete!) Ashish Pradhan Disclaimer October 21, 2009 The views expressed here are solely the author's and should not be attributed to InterGlobe Technologies or its clients.
  2. 2. Introduction: Mainframes, SoA & Legacy GOAL: All of us here understand SOA & we know Legacy- Mainframes. What relationship do they share with each other? • Over the next 15-mins, let’s explore that & it’s significance to an organization that uses a Legacy-MF Mainframes (MFs) are still around & how! • Movement to SOA has so far ignored MFs • At best, MFs have been reluctant participants Smarter action: Bring them into SOA • MFs need SOA + SOA needs MFs! My Definition of legacy: • If you do not speak SOA, you are legacy! • Corollary: If your MF speaks SOA, you are not legacy! 2
  3. 3. Origin of SOA for Legacy? 2009 2001 Opportunity exists to go 2006 ‘True Mainframe SOA’ Web Services started evolving in the distributed-platforms Web Services for MFs got (SOA was nowhere to implemented through rigid, be seen) 2004 proprietary interfaces The SOA experts on the distributed-systems had no knowledge of MF applications; the MF There was pressure to expose Web Services application experts had no knowledge of SOA from MFs too (SOA had started gaining good- (Both ignored each other!) support on the distributed-systems) It will not be wrong to say. . . For MFs, SOA did not evolve at all – Only Web Services happened! 3
  4. 4. Business Environment: Influence on SOA If SOA never evolved for Legacy system MFs . . .Is that bad? • Absolutely NOT. In fact, that is the opportunity now! SOA for distributed-systems evolved faster & has now become a victim to the hype that was created by vendors of SOA products • Inability to measure ROI tangibly for SOA has further fuelled talks • Lessons learnt here serve as valuable inputs to SOA for MFs With the economic-downturn in 2009, obituaries have started appearing about SOA • Tens-of-blogs and articles are proclaiming- ‘SOA is Dead’ • What is the truth? ? ? 4
  5. 5. Business Environment: Influence on SOA (contd) The truth is: • The term, ‘SOA’ may have fallen off books for a section of business- sponsors; but the principles of ‘service-orientation’ it proclaims are extremely relevant today! • SOA is also transforming itself and becoming more nimble, small & transparent! w c do mi n ow o sl co n E Cloud SOA Metamorphosis SaaS No separate SOA Infrastructure (Mainframe Hosted SOA Solutions) 5
  6. 6. SOA is only a concept: View Legacy differently! At the risk of sounding very simplistic, I say: ― We have got a basic SOA in place by just viewing the legacy-system differently! 6
  7. 7. Why SOA for Mainframes? Legacy-MF houses the enterprise’s assets in it! • Not reusing these assets through newer-channels (eg. Telephony (Text- to-speech data-announcements), e-Commerce, etc) is a waste! • Having a point-to-point interface is not a sustainable clean-approach • A good SOA implementation addresses both of these effectively We want Enterprise SOA, not SOA for distributed systems only! • All parts of the organization should be able to find & leverage MF-assets • A functional SOA implementation with minimal/no MF participation has limited benefits to the organization SOA for MF is the secret weapon of the CIO running an organization with legacy-MF • Remain business competitive for M&A • Integration of legacy platforms/consolidation becomes a breeze • SOA can be implemented while leveraging MF-hardware- no new boxes! 7
  8. 8. Past journeys of so-called, ‘SOA for MFs’ Common observations across the industry • Used hand-coded scripts /programs to move data from their MFs to other platforms or databases (‘Info-Integration Challenge’) • Only a very small % of enterprise data from MF was exposed through Web Services • Had problems identifying which legacy programs could be turned into a Web Service and exposed • MF Application programmers did not understand SOA/Web Services; the SOA experts from distributed-systems did not understand the MF- applications! • MF acted as a Server exposing Web Services; Never as a consumer! • Application Servers resided on another platform & accessed MF 8
  9. 9. Recent developments in SoA for MFs Common observations across the industry Key points: • Transform MF into a full-fledged SOA participant • MF can be both: A provider of enterprise services & a consumer • MF can act as a Service Intermediary • MF can now house the SOA Infrastructure; no external hardware • Data integration tools: Provide reliability & scalability Scenarios: • MFs that were Web Services enabled 5-years back do not have a complete SOA framework • Should these MFs jump & now embrace ‘True MF SOÁ’? — NO! Learnings of past do not recommend a standalone investment in SOA. It is a strategic decision not tactical! • Time the SOA-implementation to ride-along with a big-turnkey business project (Eg. M&A) 9
  10. 10. Using MF for SOA Infrastructure Key observations in support: • Inherent benefits of MF: performance, reliability & high-availability • No additional hardware investment necessary • Several Mainframe SOA solutions exist today from IBM & Vendors • IBM has taken steps to support SOA initiatives on MF IBM has introduced ‘Speciality Engines’ on MF: zIIP & zAAP • zIIP: System-z9 Integrated Information Processor • zAAP: System z Application Assist Processor • IFL (Integrated Facility for Linux) : Run Linux on MF (i.e. zLinux) 10
  11. 11. Speciality Engines on MFs Speciality Engines Advantages: • ‘Qualified load’ can be passed to ‘Speciality Engines’ – This load does not count against MIPS usage!! • Reduces load on GPP (General Purpose Processor) thereby reducing TCO • No speed capping on Specialty Engines (Not restricted to GPP speeds)! • Examples of Qualified Load: ― DB2 Processing & DB2 Queries ― Data-integration/transformation on MF for SOA ― XML Parser: Marshalling & De-marshalling ― JAVA Runtime: Consume External Web Services A game-changer from IBM: Speciality Engines • A vendor’s MF-SOA Solution that leverages Speciality Engines makes sense! 11
  12. 12. In Summary . . . A legacy-system today is no longer a challenge in the journey towards SOA Including the Mainframe as an active-participant in the SOA journey, creates an exciting opportunity to revitalize & rejuvenate the organization! 12
  13. 13. About ….. InterGlobe Technologies Part of India’s largest Travel Conglomerate– InterGlobe Enterprises(IGE) • India’s leading Value-based carrier: Indigo Airlines, belongs to our group Service Offerings • IT- Solutions & Services • Business Process Outsourcing / Off shoring Global delivery model to service clients across multiple locations • Expertise in Mainframe, Legacy environment • Application development & Maintenance services • SOA-enablement • Web Services Domain expertise • Travel, Transportation & Hospitality • Finance Copyright © 2009 InterGlobe Technologies 13