Web 20- 2: Architecture Patterns And Models For The New Internet

Speaker bio Duane Nickull Current § Chair OASIS SOA Reference Model Technical Committee (OASIS § Standard as of 2006) Community Member (Planner) Ontolog Forum § Contributor OASIS SOA Reference 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) § Author (books, white papers, technical articles0 § Speaker (Conferences, Universities …) § 2 2006 Adobe Systems Incorporated. All Rights Reserved.

Web 2.0? Does it need definition? § “Web 2.0 is the network as platform, What is it really? § spanning all connected devices” Frame? § “… an ecosystem for communicating, connecting, collaborating and creatively expressing ideas and information in revolutionary new ways” * http://www.oreillynet.com/pub/a/oreilly/tim/news/2005/09/30/whatisweb20.html 3 2006 Adobe Systems Incorporated. All Rights Reserved.

Methodology used to identify Patterns & Architecture Models Reference Refine Architectures Guide Specialized Architectures Patterns of Use Enable 6 2006 Adobe Systems Incorporated. All Rights Reserved.

Patterns from examples, Models from Patterns Architectural patterns can be distilled out of examples. § Models based on concepts to enable patterns. § Conceptual Architecture (Abstract) based on Model. § 7 2006 Adobe Systems Incorporated. All Rights Reserved.

Model Definition: Abstract lexicon capturing a generalized set of concepts and § noting their purposes and relationships to each other. Primary Audience: Entrepreneurs, Software or Enterprise Architects § Why: § Models guide all domains, whether explicit or implicit. They facilitate a common, § shared understanding or conceptualization of a domain. Famous Models: OSI 7 layer stack, OASIS Reference Model for SOA. § 9 2006 Adobe Systems Incorporated. All Rights Reserved.

Abstract (Engagement) Model for Web 2.0 Abstract Model for connecting and integrating capabilities and users. § Users Client Applications/Runtimes Patterns Connectivity/Reachability of inter action SOA Services Capabilities Don't treat software as an artifact, but as a process of engagement with your users. Tim O’Reilly 11 2006 Adobe Systems Incorporated. All Rights Reserved.

Reference Architecture A technology component view of a generalized architecture. § NB!: Abstract of all technologies (HTTP, TCP/IP java etc) and § abstract of all applications or vendor products. Agnostic to patterns of usage. Primary Audience: Software or enterprise Architects § Why: There is a great value in being able to communicate ideas and § functionality abstract of specific technologies protocols or products. These become artifacts that can be applied by architects in multiple domains. 13 2006 Adobe Systems Incorporated. All Rights Reserved.

Web 2.0 application Dev. Conceptual architecture. Controller Client Data/State Security Rendering Virtual Machine Application Management Container/Model & Media Tier Communication Services Network / Standards, Consistent Consistent Design & Technologies & Object and Event Architectural Connectivity Governance Protocols Models Models Tools Service Invocation layer Business Services Registry Service Core Rules/ Repository Container Services Tier Workflow Service Provider Interface Resource Tier = spans both tiers 14 2006 Adobe Systems Incorporated. All Rights Reserved.

Service Tier Service Invocation layer Business Service Registry Service Core Rules/ Services Repository Container Tier Workflow Service Provider Interface Service Invocation Layer Catches conditions, incoming/outgoing § communications and other events that may lead to invocation of services. Business Rules / Workflow internal processes required to fulfill service § invocation requests Service provider Interface interface to hook in existing application § functionality and offer it as services. Service Container manages the state of service invocation requests during § their entire lifecycle. Checks business rules, policies to ensure invocations are done in accordance with declared policies and rules. Core Services set of common services used by the whole platform. § RegistryRepository metadata and instance data stored during its’ lifecycle. § 15 2006 Adobe Systems Incorporated. All Rights Reserved.

Client Tier Runtimes Controller Data/State Security Rendering & Client Virtual Machine Management Container/Model Media Applications Communication Services Controller core application master logic and processing § Virtual Machine runtime environment launched and managed by § controller Security Container/Model responsible for all security aspects. § Rendering all “view” behavior for GUI’s, media integration § Data/State Management transformations, state synchronizations, § transitions, state change event generation during lifecycle of objects. Communication Services all communications management including § clientserver, host environment, nth tier resources. 16 2006 Adobe Systems Incorporated. All Rights Reserved.

Web 2.0 Patterns Patterns: a general 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… § So how to we express the pattern of Collaborative Tagging? § 18 2006 Adobe Systems Incorporated. All Rights Reserved.

Collaborative Tagging (Static) Definitions: § Tag: a label making a declaration about an object or resource. § Resource: any digital asset. Examples (nonexclusive) online content, audio files, § digital photos, bookmarks, news items, websites, products, blog posts, comments… Entity: Any human, application, bot, process or other thing (including agents acting on § their behalf) capable of interacting with a resource. 20 2006 Adobe Systems Incorporated. All Rights Reserved.

Pattern: Software as a Service (SaaS) Software Vendor Domain Sofware User Domain Design Code Build Deploy Install Configure Use FUNCTIONALITY Old School Model of Deployed on Premises M,C V Use Design Code Build Deploy FUNCTIONALITY Monitor Maintain Software as a Service Improve more … 22 2006 Adobe Systems Incorporated. All Rights Reserved.

Software as a Service Properties Installed @ Premises SaaS License Perpetual > subscription > ASP > Ad / Web 2.0 models Models Location Enterprise IT Centre > Appliance > Hosted on Network Manage ment Enterprise IT shop > ASP > Open Source > SLA with SaaS Co. * Courtesy of Fred Chong 23 2006 Adobe Systems Incorporated. All Rights Reserved.

SaaS Key Characteristics: § Networkbased access and management of software § Centrally managed § Application delivery is onetomany model (single instance, multitenant architecture) § than to a onetoone model, including architecture, pricing, partnering, and management characteristics Examples of software that can get better as more people use it: § Anti SPAM software (centralization means better spam detection) § Itunes music application (hybrid approach logs relations, choices) § http://protectpdf.adobe.com (builds up membership/trust for persistent rights § management) Google results vary based on use. § 24 2006 Adobe Systems Incorporated. All Rights Reserved.

Mashup: Client side Runtime Controller Data/State Security Rendering & Client Virtual Machine Management Container/Model Media Applications Communication Services Communication management support for many models (push, pull, § subscribe, get(), broadcast tuning…. Mashups must be capable of rendering based on interactions with § multiple services and data objects. Examples: Custom mapping applications based on commercial maps, § hybrid search services, more… Ultimate example (just IMO): § http://www.amgentourofcalifornia.com/docroot/tourtracker2/index.html § 26 2006 Adobe Systems Incorporated. All Rights Reserved.

Pattern: Persistent Rights Management (Problem statement) Lack persistent access controls to prevent § information redistribution Cannot dynamically change rights/access after § distribution Unauthorized Users Recipient Author File System Secure Pipe Approach Access Control Approach 28 2006 Adobe Systems Incorporated. All Rights Reserved.

Pattern: Persistent Rights Management Wrap and encrypt the digital asset. § Wrapper is linked to a policy: § Without complying with policy, asset cannot be opened/rendered. § Policy wrappers are inalienable from assets § Owners can dynamically change policies on assets § Multiple known implementations (MS RMS, Adobe LiveCycle, § Navisware). 29 2006 Adobe Systems Incorporated. All Rights Reserved.

More on Web 2.0 Patterns Working on book for Oreilly. § Companion website www.web20patterns.org (not live yet) § Lots of common wisdom to draw on. § Entrepreneurs who understand the patterns and can reapply them to § new business problems with have a boom! Questions? § 31 2006 Adobe Systems Incorporated. All Rights Reserved.

Web 20- 2: Architecture Patterns And Models For The New Internet

0 comments

Notes on slide 1

Favorites, Groups & Events