Sinergia entre SOA e Web 2.0: Novo contexto para as aplicações corporativas

1. Sinergia entre SOA e Web 2.0:Novo contexto para as aplicações corporativas Cezar Taurion Gerente de Novas Tecnologias Aplicadas Iniciativas Estratégicas ctaurion@br.ibm.com www.ibm.com/developerworks/blogs/page/ctaurion

2. Isto tudo faz algum sentido para vocês ? folksonomy AJAX REST Mashups RSS Wikis Social Networks Social Computing

3. O Fenômeno Wikipedia • Imaginem um projeto com as seguintes características: • Aglutinar todo conhecimento humano • Autoria colaborativa • Dezenas de línguas (+1.500.000 verbetes em inglês e + 230.000 em português) • Manter histórico das atualizações, acesso rápido, flexível nas atualizações e inserções de verbetes (1500 verbetes por dia), alta demanda (um dos dez sites mais visitados) • Como gerenciar este projeto na forma tradicional?

4. O Fenômeno das redes sociais

6. Mudanças no comportamento social… • Who do you trust? Word of mouth rank high for all

7. Personalidade de 2006: VOCÊ! “In 2006, the World Wide Web became a tool for bringing together the small contributions of millions of people and making them matter” • A Web 2.0 está criando novas fronteiras para a colaboração e a inteligência coletiva. Time, December 25, 2006

8. Social Economic Web 2.0 Technology O que é a Web 2.0? Web 2.0 is a set of economic, social, and technology trends that collectively form the basis for the next generation of the Internet - a more mature, distinctive medium characterized by user participation, openness, and network effects. Source: Web 2.0 Best Practices and Principles, O’Reilly Radar

9. O que é a Web 2.0? Web 1.0 was about connecting computers and making technology more efficient for computers. Web 2.0 is about connecting people, and making technology efficient for people. Web 2.0 changes the way businesses interact with customers Expanding from dozens of markets with millions of people to millions of markets of dozens of people

10. O contexto da evolução da internet Web 1.0 Web 2.0 Web 3D Acesso Busca Co-Criação Participar Colaborar Páginas informativas com texto e gráficos Ambiente altamente social, criado pelo usuário Usuários gerando conteúdo, blogs, wikis, mashups visando compartilhar Conteúdo Desenvolvimento de Produtos/ Serviços, Otimização do Trabalho, Educação, Comunidades Comunicação, RH, Compras, Marketing, Treinamento Colaboração, Treinamento , Marketing Negócios Tecnologia Colaboração Pessoas

11. Software development SourceForge SubVersion Rational Jazz RCS Conference Blackboards Virtual conference Community of Practice Professional development In-person Tele-conf Video Conf Jam Collaboration E-meetings IM Classroom Distance E-learning Peer-to-peer learning Virtual Univ Education Bricks & Mortar Amazon eBay Online Shopping Marketplace Video Computer Internet MMOGs Board Games Evolução das comunidades Comunidade 1.0 (Web interface) Comunidade 2.0 (Social computing) Comunidade 0.0 (Limitada pela geografia) Comunidades Digitalização

12. Web 2.0 : Internet como “The Platform” Techniques: Mash-up, wiki, tagging, blogging Tools: RSS, AJAX, PHP, Ruby Standards: REST, XHTML The Web as “The Platform” Light-weight programming models Rich user experiences Small pieces loosely joined, or “re-mixed” Software that gets better as more people use it Services, not packaged software Harnessing collective intelligence Architectural participation

13. O conceito da Cauda Longa... The Long Tail • Targeting niche markets - expanding from dozens of markets of millions of people to millions of markets of dozens of people • Examples: Google, Netflix, Amazon Network Effects • Product or service is more valuable the more people that use it (e.g telephone, email, instant messaging…) • Examples: eBay, MySpace, Craigslist…

14. Enterprise Application Long-tail Mission Critical WS WS CE & Open Source Built to Last Situational Applications Applications Long-tail & Software : Situational Applications

15. Definition: Situational Applications • Situational application development involves aggregating, customizing, or extending an existing collection of simple web services • Built to solve an immediate, specific business problem • Typically performed by non-traditional programmers (e.g., business professionals, analysts, other IT staff, etc.) • Makes use of pre-existing software components or services such as spreadsheets, report generators or vertical business applications already in use • Manipulates static and increasingly dynamic content – information-centric • Accelerated by a community-based development approach Integration is pushed to the edges and on a global scale

16. The Accelerating Evolution of Software Situational application development paradigms are emerging which will challenge traditional IT development • New tools and approaches to develop situational applications – applications built with simplicity, efficiency, and just enough function to solve the business problem at hand – are emerging • Proliferation of easy-to-use software, tools and techniques (e.g., Web 2.0, LAMP, PHP) • Wide availability of domain-specific web services (e.g., Google maps, UPS, NoAA) • Simple application paradigms to manipulate, integrate, and publish dynamic content (e.g., QEDWiki) • The rapid growth in computer literacy and non-traditional programmers • These trends will result in significant challenges for enterprise IT environments • Supporting and enabling community-based development within the enterprise • Refactoring interfaces to enterprise applications as consumable web services • Dealing with the growing heterogeneity in the IT environment • Facilitating the development, deployment, and management of situational applications • Situational application development approaches will fundamentally change the way applications are developed and deployed, accelerating the proliferation of consumable web services

17. Evolution of Enterprise Applications Applications built by LOBs and end-users, customizing and aggregating services as needed Applications initially prototyped by LOBs, then rebuilt by IT departments Enterprise applications built by IT departments Enterprise Application Evolution Web Services Enabled World Client-Server World Mainframe World Time 90’s-00 00-10’s 60’s-80’s

18. Situational Application Example – Scipionus.com Application built by one person in one day, leveraging Google maps web service Legend: – events – changes – 50 latest

19. craigslist Google Maps + = www.housingmaps.com Situational Applications: The primordial mashup

20. Mashups:Script, scrape, shred, snip, mash, map…. That is the new programming fashion.. Mashups like Coffee integrate disparate data sources through simple scripting tools by combining existing web services into entirely new applications Typically sourced from a third party via a public interface using Web feeds (e.g. RSS or Atom) and JavaScript

21. AccuWeather™ AccuWeather™ “(Web 2.0) Widget-delivered weather information allows our clieants to be more productive in utilizing AccuWeather data to identify and exploit business opportunities while at the same time helping clients manage risks imposed by adverse weather conditions.” Overview • SMB company that aggregates weather content, crushes forecasts that are consume by diverse businesses • ProfessionalPlus staff that assembles custom forecast models for businesses • ModelPlus - suite of advanced forecast modeling solutions such as StormTimer • Example: CSX - sends train route information to AccuWeather - compares with severe weather to “message” CSX systems of severe, situational conditions AccuWeather Opportunity • Backlog of custom dashboards growing fast • Customers asking for “flexible” mash-ups to meet ongoing changing business needs • Customize costs high given current technology foundation • Extend current weather content subscription to enabling user-customizable dashboards • Seeing growing number of weather widgets, branded with AccuWeather - with poor quality - potential reflection on company

22. Porque as empresas precisariam de Web 2.0?Because the Landscape has changed Causa • The World is Flat • Information Overload • Business Changes faster than IT can respond • CIOs can’t afford to serve the “long tail” Efeito • Empowerment and independence of Knowledge worker • Knowledge Worker is now the Situational Application Assembler. • Web 2.0 enables the Knowledge worker to collaborate and create “good enough” solutions that satisfy their ever changing needs Issues • Productivity of Knowledge worker – Tools for new programming models • Reliability and Manageability of decentralized IT applications • Search capabilities to enable reuse of long-tail solutions

23. IT buyers view the Web 2.0 concept favorably “Which of the following best describes your reaction to the term ‘Web 2.0’?” Strongly Negative,0% 3% Ï’ve not heard the term Web 2.0 before Negative, 3% 20% Strongly Positive Neutral,29% Positive, 44% Base: 275 IT decision-makers at US companies with 500 or more employees Note: “Don’t know” responses excluded Source: Forrester Research, June 2007 United States Web 2.0 Online Survey

24. “How businesses are using Web 2.0: A McKinsey Global Survey”

25. Embora ainda estejamos na fase do “Hype Cycle” precisamos entender o assunto e (re)agir! Visibility Post Press conf Phone Fax Tecnologias que compõem a Web 2.0 Search Engine Opt. Blogs Direct mail Word of Mouth Wikis newsgroup RSS Social networks Webcasts database Podcasts email Citizen journalism Instant messaging Tech Trigger Peak of inflated expectation Slope of enlightenment Plateau of productivity

26. July 2007 “Developing Enterprise Web 2.0 Applications” Types Of Enterprise Web 2.0 Apps

27. Junção dos mundos SOA e Web 2.0 • Web 2.0-class Apps • Web 2.0 technologies & services - defacto standards • Content/data focused • Outward-Facing • Very Loosely Coupled • Security: Assume Everything is a Threat • SOA-class Apps • Standards-based (WS-*,…, SCA) • Normalized Transactions • Inward-Facing • Somewhat loosely Coupled • Security: “lockdown” Gartner™

28. Reshaping of Enterprise Software Enterprises Putting Web 2.0 to Work • Focus on Simplicity - empowering content-centric developers • Data Driven - business value centered on content • Remixability - new business opportunities to COMBINE content • OpenAPIs - building/extending ecosystems both with ISVs & customer COLLABORATION • Rich Internet Applications - improved EXPERIENCE leads to improved revenue • User Generation Content - active participation & self organization to influence product development

29. Web 2.0 permite criar uma Global SOA Enterprises are exposing more services and feeds to the Web…and consuming more services and feeds from the Web • Exposing Enterprise Services to the Web extends your enterprise globally and simplifies: • Development • Composition of Services • Deployment and accessibility • QoS: Performance, Scale, Security

30. SOA e Web 2.0: Mudanças no contexto: processos, tecnologias, skills… Model Assemble Deploy Manage

31. SOA e Web 2.0: Mudanças no contexto: processos, tecnologias, skills… • Increasingly, applications will be developed or modified in departments and LOBs, not just in IT shops • Situational applications are being developed in simple ways (e.g., Web 2.0), and will integrate and run across different development environments (J2EE, LAMP, .Net, …) • Situational applications will integrate components from within the enterprise and from the outside (other enterprises, internet) Therefore, corporate IT will be challenged to facilitate the development, integration, and management of situational and enterprise applications

32. SOA e Web 2.0: Mudanças no contexto: processos, tecnologias, skills… Model • Gathering business requirements, discovering available services and components, and simulating the desired business processes • Compose applications that use services residing in different environments using natural metaphors (e.g., access EJB or web service from PHP) • Testing – provide the developer with an environment that resembles the deployment environment (e.g., testing solutions across multiple environments) Assemble Deploy • Configure distributed applications so that different pieces can run in their associated environments • Coordinate upgrades of dependent pieces across heterogeneous environments using a common set of tools Manage • Facilitate problem determination in a mixed environment (e.g., stitching together traces and logs from different application environments) • Autonomic resource management (e.g., tuning and load balancing optimized across application environments)

33. Obrigado pela Atenção! Cezar Taurion Gerente de Novas Tecnologias Aplicadas Iniciativas Estratégicas ctaurion@br.ibm.com Visitem meu blog em: www.ibm.com/developerworks/blogs/page/ctaurion