The document discusses Web 2.0 and service-oriented architecture (SOA). It provides examples of Web 2.0 concepts given by Tim O'Reilly and lists some common Web 2.0 patterns like tagging, mashups, and software as a service. The document also presents a reference architecture for Web 2.0 applications and discusses how SOA and service-oriented clients relate to Web 2.0. It identifies some potential anti-patterns for SOA and Web 2.0 applications.

1. Web 2.0 and SOA that will make your Web site purr like a Porsche Duane Nickull Senior Technical Evangelist

2. Speaker bio - Duane Nickull Current Chair - OASIS SOA Reference Model Technical Committee (OASIS Standard as of 2006) Community Member (Planning Committee) - Ontolog Forum Contributor - OASIS SOA Reference Architecture Technical Committee Contributor - OASIS Service Component Architecture Technical Committee Past: Contributor/architect - W3C Web Services Architecture Chief Architect/Chair - United Nations CEFACT Technical Architecture (SOA) Chair - OASIS eBusiness SOA Technical Committee Chief Architect - ebXML Technical Architecture (first major SOA) Co-inventor - GoXML Contextual XML Search (51 unique patent points) Co-Inventor - XML Commerce Pro (1997 ) first fully XML commerce engine Author (books, white papers, technical articles) Speaker (Conferences, Universities …) My Band http://www.myspace.com/22ndcentury

3. And previous owner of these…. Puuurrrrr!

4. And most recently…. Part of a research project to capture knowledge in this book using normative architectural artifacts on Web 2.0.

5. So what does the future look like? DEMO

6. So what is Web 2.0? Something that people are struggling to understand No common architecture Multiple definitions Contentious So how can we capture the knowledge?

7. Where to start?

8. What architects use to capture knowledge

9. "Example isn't another way to teach; it's the only way" -- Albert Einstein

10. Definition: What examples did Tim O’Reilly give? Web 2.0 Google AdSense Flickr BitTorrent Napster Wikipedia Blogging upcoming.org and EVDB search engine optimization cost per click web services participation wikis tagging (“folksonomy”) syndication Web 1.0 DoubleClick Ofoto Akamai mp3.com Britannica online personal websites evite domain name speculation page views screen scraping publishing content management systems directories (taxonomy) stickiness

11. Methodology Used to Capture Web 2.0 Knowledge * based on Design Patterns Reference Architectures Domain specific requirements Specialized Architectures Solution Patterns Models Abstract Concrete Guide Refine Enable Account for

12. Patterns Repeatable solution to a commonly occurring problem. Patterns can be repurposed across multiple domains and used to solve recurring problems there within. Example: Collaborative Tagging (aka Folksonomy). Can be used for audio files, video files, text files, binaries, people…

13. Some Web 2.0 patterns? Architectures of Participation Pattern, Small Pieces Pattern, Loosely Joined Pattern, The Platform Pattern, Software as a Service, Data is the Next “Intel Inside”, Ease of Development, Innovation in Assembly, Mashup, Leverage Commodity Economics, Virtualisation: Run on someone else's data center, The biggest pile Pattern, Opting out, not opting in, Voting (explicit and implicit), The Catalog (flickr photos, youtube, mp3), Real Time Auction?, Non-intrusive ads, Front-end/back-end separation reliable back-end, Ease of Development, Embed codes, Redistributable, Self-service (ebay, craigslist), REST, Tags, Comments and community, Plug-in business models, Interfaces, Search, Instant Update (Ajax), Ratings, Service Oriented Architecture (SOA) , Rankings and ways to keep score, The Link, Sensors, Desktop Controller, Reputation systems (pagerank), Blogrolls, Share Buttons, Widgets and Gadgets, Feeds (RSS, Atom, Twitter, FB), The Platform Pattern, Software as a Service, Data is the Next “Intel Inside”, Ease of Development, Innovation in Assembly, Mashup, Leverage Commodity Economics, Virtualisation: Run on someone else's data center, The biggest pile Pattern, Opting out, not opting in, Voting (explicit and implicit), The Catalog (flickr photos, youtube, mp3), Real Time Auction?, Non-intrusive ads, Front-end/back-end separation reliable back-end, Ease of Development

14. So how does this affect the way you architect your IT Infrastructure?

15. Web 2.0 Reference Architecture Controller Data/State Management Communication Services Design, Development & Governance Tools Client Application Tier Security Container/Model Virtual Machine Rendering & Media Service Tier Registry- Repository Service Invocation Layer Service Provider Interface Service Container Business Rules/ Workflow Resource Tier EIS Databases Directories ECM Repository Message Queues Legacy Systems Consistent object & event models Consistent architectural models Core Services Standard Technologies & Protocols

16. Service Oriented Computing Re-purposing core functionality as service to be consumed. But wait! What about the clients? Do they have to be different? Service Oriented Clients (SOC’s)? Service Oriented Clients are, in most cases, Web 2.0 applications!

17. Service Oriented Clients - Web 2.0 Application Architecture Mashing up multiple formats Using services to deliver rich user experiences Rendering/Media engines let users control the way they use your applications. Are no longer standalone - use knowledge of other users applications.

18. People are starting to see “BAD” patterns too….

19. Anti patterns to SOA/Web 2.0? Composite Applications. Based on UML Composition relationship, yes! Aggregate Applications is more accurate. Blob - A large class with too many attributes and is the "heart" of the system. Walled Gardens – the open web is the way to go! Spaghetti code - Program code that has no structure (lots of “goto” statements) Golden Hammer/Swiss Army Knife - Forcing everything to fit a selected tool More?

20. Revolutionizing how the world engages with ideas and information In true Web 2.0 manner: You are hereby free to use these slides in any way you want. You are responsible for Making sure you have any rights associated with any graphics etc and have to take responsibility for honoring any copyrights etc. PLEASE: make sure the logo owners are cool if you want to use them! No attribution is necessary - they are yours to claim as your own and go out and do with what you want!