Core Saas Design and Architecture Patterns

®

Copyright 2008 Adobe Systems Incorporated. All rights reserved.

Core Saas Design and Architecture Patterns

Duane Nickull

Sr. Technology Evangelist

Adobe Systems

®


Ich bin?

  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

  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

®


Agenda

  A real hard look at SOA

  SaaS Parents -> MVC and SOA.

  SaaS on one machine vs ASP/Cloud Models

  Business advantages of SaaS

  Changes to architecture

®


Evolution enabling SaaS

Monolithic spaghetti beasts

Structured Monoliths Client - Server

3 tier

Services

N tier Distributed Objects

Components Things that use Services

BPM Mashups SaaS RIA SCA Aggregate Apps

®


Fragen - SOA, Services or SaaS…

  Ganz Fragen!

®


1996 –remember this slide

THING ONE THING TWO

THING THREE

The Internet

®


1998…

THING ONE THING TWO

THING THREE

XML

®


2001…

THING ONE THING TWO

THING THREE

Web Services

®


2003…

THING ONE THING TWO

THING THREE

SOA

®


2005…

THING ONE THING TWO

THING THREE

SaaS

®


2008 (The marketers got lazy perhaps??)

Now it’s just the cloud

THING ONE THING TWO

THING THREE

®

Copyright 2008 Adobe Systems Incorporated. All rights reserved. 12

Pragmatics: How do architects capture knowledge?

Web Services live here.

SOA FIRST!

®


So what is SOA exactly?

  An Architectural Paradigm for organizing and using distributed capabilities that may be under the control of different ownership domains.

  A framework for matching needs and capabilities.

  A view of architecture focusing on “Services” as a mechanism to allows interactions between those with needs and capabilities.

  A way of thinking about problems

®


Core Model for SOA

®


Service Interaction -> Behavior & Information Models

®


Real World Effect

®


Service as an action Boundary

Service

Capabilities

Needs

®


Agenda






®


MVC – early ancestor of SaaS?

®



®


Agenda






®



®


Pattern of SaaS – different domains of ownership

23

Transparency horizon Ownership horizon

®


Use of SaaS with Virtualization

24

The Cloud

Virtualization – Logical and Physical no longer map 1:1

®


Agenda






®


SaaS early innovation

®


Effect

  Software that gets better the more people use it!

®


Software that gets better the more people use it?

  Gmail – why?

®


How it works

29

Pattern Recognition

®


Software that gets better the more that people use it 2

  Google Search – Why?

30

®


Agenda






®


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

®


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 Core Services Business Rules/ Workflow

Resource Tier EIS Databases Directories ECM Repository

Message Queues

Legacy Systems

•  Consistent object & event models •  Consistent architectural models

Standard Technologies & Protocols

®


App Server

Communication Tier

Business

Tier

Integration Tier

Resource Tier

DBMS LDAP CRM/ ERP/CM

Etc..

Synchronization Service

Business and Transaction Logic

Connectors to Data and Legacy Systems

data

data

data

Example applications:

•  Business analytics

•  Order processing systems

•  Call-centre management applications

Customers looking to manage data which needs to be synchronised across tiers and enterprise integration to existing systems and infrastructure

push() subscribe()

Pattern: Synchronized Web

®


App Server

Communication Tier

Business

Tier

Integration Tier

Resource Tier


Etc..

Synchronization Service



data

data

data


•  Business analytics

•  Order processing systems

•  Call-centre management applications

Customers looking to manage data which needs to be synchronised across tiers and enterprise integration to existing systems and infrastructure

push() subscribe()


®


App Server

Communication Tier

Business Tier

Integration Tier

Resource Tier


Etc.

Synchronization Services




•  Real-time stock monitor

•  Real-time news feed applications

Customers looking to integrate real-time third-party data feeds with no screen refresh and no client/server polling External

App


®


Adobe use of WS and SAML in LC Rights Management

®


Thank you!

Q&A Duane’s World TV

”Wer nicht fragt, bleibt dumm!”

Core Saas Design and Architecture Patterns

Documents

mvc early

centre management

rights reserved

transaction

enterprise

aspcloud models

synchronization

legacy systems