Web 2.0 Design Patterns, Models and Analysis

2005 Adobe Systems Incorporated. All Rights Reserved.1

Web 2.0 Design

Patterns, Models, and

Analysis

Duane Nickull

Senior Technical Evangelist


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


And most recently….

Part of a research project to

capture knowledge in this book

using normative architectural

artifacts on Web 2.0.


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?


What architects use to capture knowledge


Web 2.0 - Where Does it Begin / End?


The Growth of Mobility: Web 2.0 Goes Beyond Wires


Definition: What Does Tim O’Reilly Say?

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


Methodology Used to Capture Web 2.0 Knowledge *

based on

Abstract

Concrete

Guide

Refine

Enable

Account for

Design Patterns

ReferenceArchitectures

Domain specificrequirements

SpecializedArchitectures

Solution Patterns

Models


Patterns


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…

122007 Adobe Systems Incorporated. All Rights Reserved.

Common Web 2.0 Patterns

Collaborative Tagging (folksonomy)

Synchronized Web

SOA

SaaS, DaaS (variations of SOA)

Persistent Rights Management

Mashup

Rich User Experience (a.k.a. RIA,knowing something about yourusers)

Participation/Collaboration(harnessing collective intelligence)

Adaptive Software

Microformats (a.k.a. fine grainedcontent accessibility)

Declarative Living / Tag Gardening

Incremental Update (a.k.a. “AtomicParticle Update”)

… (more)


Models

The model for engaging using the

internet as a platform to span all

connected devices, humans and

applications.


Models

Definition: Abstract lexicon capturing a generalized set ofconcepts and noting their purposes and relationships toeach other.

Primary Audience: Entrepreneurs, Software or EnterpriseArchitects

Why:

Models guide all domains, whether explicit or implicit. They facilitate acommon, shared understanding or conceptualization of a domain.

Famous Models: OSI 7 layer stack, OASIS ReferenceModel for SOA.


Model for the Old Web -> Client Server

Server

Client


Abstract Model for Web 2.0

Abstract Model for connecting and integrating capabilities and users

Patterns of interaction

“Don't treat software as an artifact, but as a process of engagement with your

users. “

- Tim O’Reilly

Users

Services

Capabilities

Client Applications/Runtimes

Connectivity/Reachability

SOA


Reference

Architecture


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,

developers

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.


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

TierRegistry-

Repository

Service Invocation Layer

Service Provider Interface

Service Container Core ServicesBusiness Rules/

Workflow

Resource Tier EIS Databases DirectoriesECM

Repository

Message

Queues

Legacy

Systems

• Consistent object & event models

• Consistent architectural modelsStandard Technologies

& Protocols


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!


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.


Enterprise Focus

on Web 2.0


Enterprises Want the Patterns of Web 2.0, too!

Distributors& Agencies

Internal Processes ERP / ECM / CRM / BPM / Accounting

Customers& Citizens

Suppliers &Contractors

ENGAGEMENT PROCESSESNew account opening, Broker productivity, Grant

administration...

Trust your users

Rich user experience

Folksonomy

RIAIdentity 2.0

The long tail…Mashups

Engaging yourusers

SOAMicroformats

Semantics Loose coupling


The Engagement Gap

Frustrating delays, lost revenue, information loss, non-compliance...



Customers& Citizens



Using the Web 2.0 Model to Close the Engagement Gap



Customers& Citizens


Users

Services

Capabilities

Client Applications/Runtimes

Connectivity/Reachability

Enterprise2.0!

Web 2.0!


Amgen Tour Tracker (mash-up excellence)


So what is possible?

TV, Internet convergence (now)

Custom loyalty is gone (now)

Web 2.0 Design Patterns are top enterprise focus

(now)

Democracy, peace, ideas all flowing (now)

Spin offs galore ( ******* 2.0)

You are going to leave here and build the future (in

a few minutes)


Thank you!

Q&A

Yes - this is the same pantone!


Revolutionizinghow the world engages

with ideas and information