Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

Convergence in Enterprise IT ... the renaissance period

Media, messaging and telecommunications convergence is now accepted as the norm. Convergence has resulted in greater consumer choice, lower costs and incredible innovation. It is important to note that even incumbent vendors in this space have much to gain from such convergence as it results in the potential to offer higher value services to customers, thus creating more revenue opportunities.

Enterprise IT has not yet seen convergence come home. We continue to create separation between BPM, SOA, EDA, WOA, SaaS, Cloud computing and more. Unlike the case of telecommunications convergence, however, in the enterprise IT world the incumbents are actually not incentivized to fuel convergence as they continue to "cash in" on old investments, slightly refreshed in some cases.

Fortunately, all hope is not lost! As open standards focused on interoperability become more pervasive, many traditional technological
boundaries are rapidly coming down and falling victim to convergence. Open source further accelerates the process by being the breeding grounds of untethered disruptive innovation resulting in simple, easy to use technologies which are made available freely, thus fueling rapid adoption.

In this talk I explore the growth of convergence in enterprise IT and the radical simplicity it is delivering to enterprise architects & developers.

  • Be the first to comment

Convergence in Enterprise IT ... the renaissance period

  1. 1. Convergence in Enterprise IT .. the renaissance period Sanjiva Weerawarana, Ph.D. Founder, Chairman & CEO, WSO2 Founder & Director, Lanka Software Foundation Member, Apache Software Foundation (Emeritus) Director, Open Source Initiative Visiting Lecturer, University of Moratuwa, Sri Lanka SOA Kongress, Mainz, Germany, October 29, 2008
  2. 2. About me <ul><li>Currently Founder, Chairman & CEO of WSO2 </li></ul><ul><ul><li>Open source SOA company </li></ul></ul><ul><li>Previously 8 years in IBM Research </li></ul><ul><ul><li>Part of IBM team that defined Web services / SOA technologies </li></ul></ul><ul><ul><ul><li>Worked closely with Prof. Dr. Frank Leymann </li></ul></ul></ul><ul><ul><li>Co-author of WSDL, BPEL4WS, WS-Eventing, ... </li></ul></ul><ul><li>Long time open source person </li></ul><ul><ul><li>Co-author of Apache SOAP, Apache Axis 1 & 2, Apache BSF, Apache WSIF, ... </li></ul></ul><ul><ul><li>Member of Apache Software Foundation </li></ul></ul><ul><ul><li>Emeritus Board Member of Open Source Initiative </li></ul></ul><ul><li>Founder and Director, Lanka Software Foundation </li></ul><ul><ul><li>Sri Lanka is leading contributor to open source in Asia </li></ul></ul><ul><li>Visiting Lecturer, Univ of Moratuwa </li></ul>
  3. 3. Outline <ul><li>Enterprise IT strategies </li></ul><ul><li>Open standards </li></ul><ul><li>Open source </li></ul><ul><li>Converging patterns into a core long term foundation </li></ul><ul><li>Technology </li></ul><ul><li>Summary </li></ul>
  4. 4. Enterprise IT strategies EDA SOA BPM Tuple spaces SaaS Cloud EAI
  5. 5. Strategies and hype curve Trough of Disillusionment Peak of Inflated Expectations Slope of Enlightenment Plateau of Productivity Technology Trigger EDA BPM SOA Tuple spaces SaaS Cloud EAI
  6. 6. IT strategy and products <ul><li>Each strategy is an opportunity to sell a new product! </li></ul><ul><ul><li>SOA: ESB / EAI: JMS message bus / ... </li></ul></ul><ul><li>From a IT vendor perspective, this is great </li></ul><ul><ul><li>Every time a new strategy heats up, lots of opportunities to sell everything from products to consulting to services </li></ul></ul><ul><ul><li>Often products are not new .. recycled / rebranded </li></ul></ul><ul><li>From a customer perspective, this is terrible </li></ul><ul><ul><li>Simply moving from one failed/incomplete project to the other </li></ul></ul>
  7. 7. Dilemma! <ul><li>Is there a method to the madness? When will it “end”? What is fundamental to enterprise IT? How will vendors support it? </li></ul><ul><li>What incentive do vendors have to really create a simple foundation? </li></ul>
  8. 8. Keys to enterprise IT convergence <ul><li>Open standards that enable interoperability </li></ul><ul><li>Open source as the innovator and driver of interoperability </li></ul><ul><li>Minimal, simple technology foundation </li></ul><ul><ul><li>XML, messages & services </li></ul></ul><ul><li>Customers driving vendors to deliver convergence </li></ul>
  9. 9. Open standards
  10. 10. Open standards: portability <ul><li>90s view </li></ul><ul><li>Protected customers against vendor lock-in </li></ul><ul><ul><li>Response to 80s monopolistic era </li></ul></ul><ul><li>Focus on intra-enterprise productivity and IT cost reduction </li></ul><ul><li>Examples: J2EE, JMS, CORBA, DCOM </li></ul><ul><li>Implications: </li></ul><ul><ul><li>Scuttled innovation as APIs became fixed </li></ul></ul><ul><ul><li>Created islands in the enterprise </li></ul></ul><ul><ul><li>Fueled open source as the place to innovate </li></ul></ul>
  11. 11. Open standards: interoperability <ul><li>21 st century view is “object oriented standards” or standards focused on interoperability </li></ul><ul><ul><li>How you implement is not my business </li></ul></ul><ul><ul><li>Let's agree on how I will interact with you </li></ul></ul><ul><li>Allow vendors to compete on implementation quality, productivity, performance etc. </li></ul><ul><li>Use the best tool for the job – interoperability is all that matters </li></ul><ul><li>Examples: WS-*, SOA standards </li></ul>
  12. 12. Enterprise benefits <ul><li>Enables greater vendor choices </li></ul><ul><li>Supports internal heterogeneity and creativity </li></ul><ul><li>Allow using newer, higher productivity tools for each task </li></ul><ul><li>Overall cost savings, greater agility due to information hiding behind interoperable interfaces </li></ul>
  13. 13. Open source
  14. 14. Open source <ul><li>Basic idea: write software and give it away with lesser constraints than proprietary software </li></ul><ul><ul><li>(Not to be confused with public domain software) </li></ul></ul><ul><li>Reach of Internet allowed people to collaborate to solve common problems </li></ul><ul><li>Open source distribution natural mechanism to distribute results of shared community work </li></ul>
  15. 15. Enterprise software and open source <ul><li>Used to be that if you can't afford the real thing you “buy” an open source option </li></ul><ul><ul><li>JBoss, MySQL reached critical mass with that </li></ul></ul><ul><li>Since mid-90s open source became the primary innovator for lower level components, esp. in Java world </li></ul><ul><ul><li>Ask your developers how many libraries they download and use </li></ul></ul><ul><li>In recent history, a lot of new innovation has come from open source </li></ul><ul><ul><li>Ruby on Rails, Grails, Synapse, CouchDB, Hadoop, SVN, GIT, ... </li></ul></ul>
  16. 16. Open source ... <ul><li>... is no longer the place to go if you can't afford the real thing: </li></ul><ul><li>Its where the real thing is happening! </li></ul><ul><li>Why? Because open source innovators do not have to weigh revenue implications brought on by the innovation. </li></ul><ul><li>Real freedom to innovate! </li></ul>
  17. 17. Open source & the enterprise <ul><li>Enables internal innovation </li></ul><ul><ul><li>“We're running an innovation project and have installed a LAMP stack” </li></ul></ul><ul><li>Enables developer “stickiness” because of feeling of ownership </li></ul><ul><li>Brings out passion and commitment of your developer community </li></ul><ul><li>Enterprises are source of open source innovation! </li></ul><ul><ul><li>Majority of software is written by enterprises, not IT vendors </li></ul></ul><ul><ul><li>Lots of wasted effort across similar enterprises </li></ul></ul><ul><li>Lower cost </li></ul>
  18. 18. Open source & academia <ul><li>Academia is slowly but surely seeing the benefits of participating in open source and building on it </li></ul><ul><ul><li>Example: Univ. of Stuttgart's IAAS </li></ul></ul><ul><li>My view: academia is the research division of open source! </li></ul><ul><ul><li>Great source of inspiration for real projects at all levels </li></ul></ul><ul><ul><li>Results can become adopted much faster than before </li></ul></ul><ul><ul><li>Justify R&D spending by practical impact </li></ul></ul>
  19. 19. Deploying open source in the enterprise <ul><li>First of all, open source is not the only innovator and will never be the only source of all the software technology </li></ul><ul><li>Interoperability is key – select systems that meet your chosen interop requirements </li></ul><ul><li>Encourage internal innovation by going beyond the comfort zones of Java and .Net </li></ul><ul><li>Engage with the community and vendor of open source products </li></ul><ul><li>Support continuous innovation by buying support </li></ul>
  20. 20. Back to enterprise IT convergence ..
  21. 21. Unifying principles for IT convergence <ul><li>XML as the universal data model </li></ul><ul><li>Message as the fundamental entity </li></ul><ul><ul><li>Event as a special case </li></ul></ul><ul><li>Service as the abstraction of business function </li></ul><ul><li>Is this a new thing? NO! </li></ul><ul><ul><li>Analogy in economy: English / documents / services </li></ul></ul>
  22. 22. XML <ul><li>Provides an internationalized universal data model that is supported everywhere by everyone </li></ul><ul><li>Not the fastest / most efficient / cheapest / ... </li></ul><ul><ul><li>But it works interopably everywhere </li></ul></ul><ul><li>XML Schema gives a standard way to document your XML structures </li></ul><ul><li>Using XML as the interoperable format for communication results in maximum reach </li></ul>
  23. 23. Message <ul><li>Fundamental abstraction of a business interaction </li></ul><ul><li>Basically, headers + actual message (payload) </li></ul><ul><li>Everything can be modeled this way – events are also messages, but usually not targeted to a single receiver </li></ul>
  24. 24. Service <ul><li>Offers a business level function </li></ul><ul><ul><li>Groups together collection of message exchange patterns </li></ul></ul><ul><li>Interaction via interoperable standards </li></ul><ul><li>Internal implementation not the business of the consumer! </li></ul><ul><li>Can be realized in many different ways </li></ul><ul><ul><li>Objects / classes </li></ul></ul><ul><ul><li>Workflows </li></ul></ul><ul><ul><li>Rules </li></ul></ul><ul><ul><li>Adapters to legacy systems </li></ul></ul><ul><ul><li>CICS transactions </li></ul></ul>
  25. 25. Example: BPM <ul><li>BPEL is now accepted as the key standard for workflow </li></ul><ul><ul><li>Well not quite, BPEL + extensions (BPEL4People) </li></ul></ul><ul><li>BPEL is actually a programming language which has fundamental support for XML, message and services! </li></ul><ul><ul><li>And special features that make it suitable for workflow characteristics such as long running nature </li></ul></ul><ul><li>Special tools etc. are needed but from an enterprise architecture perspective, deploying a BPM strategy is now the same as deploying an SOA strategy </li></ul>
  26. 26. Example: EAI <ul><li>EAI: Message based integration of internal systems </li></ul><ul><li>Instead of using proprietary message formats and protocols, use interoperable standards so that EAI type integration can go across not only your Java systems but also your Windows systems and more </li></ul>
  27. 27. Example: EDA <ul><li>Events are messages which are typically delivered not based on a direct recipient but rather based on the “subject” or “topic” of the message </li></ul><ul><li>Allows decoupling of source and recipient: scales better as number of systems increases </li></ul><ul><li>Modeling as services gives flexibility to integrate in an event driven manner or directly </li></ul>
  28. 28. Convergence <ul><li>Enterprise IT strategies will come and go and will all travel the hype curve </li></ul><ul><li>Fundamental core of XML, messages, services will not go away </li></ul><ul><li>All current strategies can be realized on this core! </li></ul>
  29. 29. Technology <ul><li>(I will use WSO2 technology to briefly illustrate what this can be like – we're not the only game in town!) </li></ul><ul><li>Core of convergence is an SOA framework that supports XML, messages and services natively and at its core </li></ul><ul><ul><li>Not acceptable to layer those abstractions on something else </li></ul></ul><ul><ul><li>No, J2EE pretending to be an SOA platform does not count! </li></ul></ul>
  30. 30. WSO2 SOA suite
  31. 31. Example: WSO2 technology at CA <ul><li>Strategies: </li></ul><ul><li>BPM </li></ul><ul><li>EAI </li></ul><ul><li>EDA </li></ul><ul><li>SOA </li></ul><ul><li>MDM </li></ul><ul><li>all realized through XML, messages and services! </li></ul>
  32. 32. Summary <ul><li>Enterprise IT has been made complicated by vendors creating new buzzwords every few years to sell more stuff </li></ul><ul><li>Fundamentals of enterprise IT are simple: driven by principles of SOA </li></ul><ul><li>Open source is no longer about “poor man's software” </li></ul><ul><li>Open standards and open source are leading the way of the enterprise IT convergence renaissance </li></ul>
  33. 33. Questions? Contact:
  34. 34. The open source SOA company