Two-Day Seminar: Cloud Computing for Architects


Jason Bloomberg, President of ZapThink, will be delivering this two-day workshop in London on March 15 & 16, 2012, in partnership with IRM UK.

Click here for more information and to register!

 

Featured

LZA SOA & Cloud Training & Certification: DC – April 9-12, 2012


LZA SOA & Cloud Training & Certification: DC – April 9-12, 2012
Monday April 9, 2012-Thursday April 12, 2012
Dovèl Technologies, Inc.
7918 Jones Branch Drive
Suite 100
McLean, VA 22102

Price: $1,995.00 (including $500 early discount) [converted to 1995.00 USD]

 

ZapThink SOA Training & Certification: The Leading Vendor Independent, Architect-Focused SOA Training

ZapThink’s Licensed ZapThink Architect (LZA) SOA Training & Certification Boot Camp is recognized around the world as the best single Service-Oriented Architecture training course available anywhere.

The LZA SOA Boot Camp is an intensive, four day “fire hose” of information that prepares you to succeed with your SOA efforts, whether you’re just beginning them or are well down the road with SOA. ZapThink’s LZA SOA Training is the only public course that ZapThink offers, reflecting the best thinking and research that ZapThink produces.

 

ZapThink’s LZA SOA training & certification has no prerequisites, and is designed for architects, but appropriate for people with different roles and levels of expertise. This course is valuable for anyone who wants in-depth knowledge about how to succeed with SOA.

 

What makes the LZA SOA Boot Camp so special?

    • Vendor independent – We discuss vendors in context, both good and bad. You get a balanced perspective on each vendor we discuss.
    • Architect focused – The course concentrates on what architects have to do to be successful with SOA in their own organizations. We balance technology details with organizational approaches. If you’re not an architect you’ll learn how to think like one in this class!
    • Practical – we connect theory to practice with what really works in organizations like yours.
    • Current – we refresh the course on a regular basis to reflect the latest SOA best practices, as well as how SOA relates to other architectural challenges in the enterprise.
    • Enterprise context – SOA is an approach to organizing enterprise IT resources to meet changing business needs. We place SOA into the context of large organizations, with complex, heterogeneous IT environments and all the politics and bureaucracy that every large organization faces.
    • Globally recognized certification – Everybody who completes the LZA SOA Boot Camp obtains a certificate representing their LZA credential, giving you the right to call yourself a Licensed ZapThink Architect with all the privileges that come along with this exclusive credential.
    • Led by globally recognized SOA thought leader – All ZapThink’s courses are developed and led by Jason Bloomberg, ZapThink Managing Partner. Jason has been an analyst with ZapThink since 2001 and is the co-author of Service Orient or Be Doomed!
    • Not too technical, not too high-level – Unlike courses offered by others, we cover the technology without getting lost in the details. We discuss the big picture but connect it to the day-to-day reality of the IT shop.
    • Available around the world – See the event schedule on this page for all the locations we’re offering the LZA SOA Boot Camp!

REGISTER

LZA SOA Boot Camp Version 9.0

Day 1

Registration: 8:00 to 8:30 AM
LZA Introduction

Module 1: The Enterprise Context for SOA

  • Business Constant: Change
  • We’ve had IT challenges for years
  • If you are in a Hole, Stop Digging!
  • The Voice of Doom?
  • Business Agility
  • What is SOA?
  • Services: Lego “Ilities”
  • Composability & Business Services
  • Why SOA?
  • SOA by Any Name
  • SOA = Best Practices
  • Iconoclastic vs. Dogmatic Architecture
  • Thinking Outside the SOA Box
  • Business Drivers for SOA
  • When Not to Apply SOA
  • The Wrong Question!
  • The Distributed Computing Pendulum
  • SOA: Paradigm Shift?
  • So, How to Implement SOA?
  • There’s No Such Thing as a SOA Wizard!
  • Is SOA New?
  • XML to the Rescue!
  • What about Web Services?
  • Pros & Cons of Web Services
  • What about REST?
  • Architectural Styles
  • What is Architecture?
  • Architecture is not About the Technology
  • Architecting SOA: Beyond Use Cases
  • SOA Implementation as Complex System
  • Examples of Complex Systems
  • The Focus of CSE
  • CSE: Overall Coherence
  • Governance: Architecting People
  • Achieving Business Agility
  • Quality & Complex Systems
  • The SOA Quality Star
  • Best Effort SOA
  • SOA as Enterprise Architecture
    • The Zachman Framework
    • Pros & Cons of Zachman
    • The Enterprise Context for SOA

     

  • Cloud Computing: Old Wine in New Bottles
    • Formal Definition of Cloud Computing
    • Relationship between Cloud & SOA

     

  • Services Thinking
  • Why is SOA Difficult?
  • Case Studies: Mini-Studies on SOA Use
    • Information Sharing: FAA
    • Reducing Integration Costs: Aeroplan
    • Compliance & Volume: Wells Fargo Bank
    • Meeting Client Needs: MITRE

Module 2: SOA Design Principles

    • Design Principle #1: Abstraction
      • What’s a Service?
      • Levels of Service Abstraction
      • Service as Interface & Implementation
      • Consumers & Providers
      • What are Services? (Technically, Service interfaces)
      • Interoperability vs. Portability
      • Service Interfaces Aren’t Good Enough!
      • Abstractions: Simple on the Outside
      • Abstraction = Working Illusion
      • Building a Working Illusion
      • The Fundamental Technical Challenge of SOA

 

  • SOA Design Principle #2: Standardized Service Contract
    • What’s a Service Contract?
    • Service Contract vs. Service Description
  • Design Principle #3: Encapsulation
    • What’s NOT in the Contract
  • Design Principle #4: Discoverability
    • What are Metadata?
    • Metadata for SOA
    • SOA Registry as “Discovery Agency”
    • Location Independence
  • Design Principle #5: Reusability
    • Reusability vs. Usability
    • Achieving Reusability: Service Agnosticism
    • Designing for Reuse: Agnostic Context
    • Reuse over Time
  • Design Principle #6: Granularity
    • Key Service Abstraction Enabler: Proper Granularity
    • Granularity Example
    • Achieving Proper Granularity
    • Zeroing in on Proper Granularity
    • Example: Too Fine Grained vs. Too Coarse Grained
    • Service Refactoring
  • Design Principle #7: Autonomy
    • Autonomy Issue: Overlapping Functional Control
    • Autonomy Issue: Concurrency
    • Autonomy Issue: Dependency
  • Design Principle #8: Loose Coupling
    • What about Coupling?
    • Full Decoupling?
    • Loose Coupling: Separation of Concerns
    • Levels of Coupling
    • Loose Coupling and Context
  • Design Principle #9: Statelessness
    • Maintaining Process Instance State
    • “Stateful Services”
  • Design Principle #10: Composability
    • Metadata-Driven Applications
    • Programmatic vs. Declarative
    • Challenges with Declarative Approach
  • Case Study: ABN Amro

Exercise: SOA Return on Investment

Module 3: The SOA Reference Architecture

  • What is a Reference Architecture?
  • Recommended SOA Reference Architecture Structure
  • What’s Different about a SOA Reference Architecture?
  • End-to-End Architecture: The SOA Metamodel
    • SOA Foundation: Model-Driven Architecture
    • SOA Foundation: The 4+1 View Model

     

  • The Agility Model
  • Service Architecture
    • Building the Service Model
    • Introducing “ZapElectric”
    • ZapElectric Service Model
  • Service Types
    • Entity Services
    • Task Services
    • Utility (IS) Services

     

  • Service Relationships Example
  • Process Isomorphism
  • Service Layers
    • Typical Service Layers
    • ZapElectric Service Layer Model

     

  • Component & Implementation Models
  • ZapElectric Logical Architecture Model

Homework: Service ModelClass Ends at 5:00 PM

Day Two

Class Begins at 8:30 AM

Module 4: Intermediaries & Integration

  • SOA Infrastructure Starting Point: The Intermediary
  • Some Intermediary Roles
  • Intermediaries and Service Façades
  • SOA “Magicians’ Tricks”
    • Multiple Interfaces per Implementation
    • Multiple Implementations per Interface
    • Multiple Interfaces per Business Service

     

  • Actualizing the Business Service Abstraction
  • Intermediaries & Messaging
  • Buying an Intermediary?
  • The Great ESB/SOA Middleware Boondoggle
    • Buy More Middleware for SOA?
    • ESB Federation?
    • Compounding the Problem: No Clear ESB Definition
    • The ESB Pattern
    • Do You need an ESB for Service Mediation?

     

  • Intermediary-Based Service Abstraction
  • Another Approach: XML Appliances
  • Building Intermediary-Based SOA Infrastructure
  • SOA Message Exchange Patterns
  • SOA Tenet: Asynchrony
  • Messages vs. Events
  • Business Driver: Visibility
  • Visibility & Heterogeneity
  • SOA, Integration & Legacy
  • Exposing Existing Capabilities
  • The Continued Value of Legacy
    • Legacy Migration
    • Legacy Enablement
    • Legacy Rejuvenation
    • Migration vs. Rejuvenation
    • Business Driver: Cost Savings
    • Reducing Integration Cost

     

  • Case Study: SOA at The Hartford

Module 5: The Role of Data & Semantics

  • The Role of Data
    • Data: Foundation for SOA
    • The Data Services Layer
    • Application Services vs. Data Services
    • Designing Data Services
    • Performance vs. Flexibility
    • Supporting Data Services with Data Integration
    • Leveraging Data Services Layer
  • Semantics and SOA
    • Semantic Level Understanding
    • Role of Application Semantics
    • Semantics: The Greatest Integration Challenge of SOA
    • Still a Manual Process
    • Resolving Semantic Issues
    • Semantic Model Example: Maritime Information Exchange Model
    • MIEM Business Case
    • Best Practices in Industry
    • Industry-Specific Semantic Standards
    • Principal Features of MIEM
    • Vessel State & Event Relationships (XML)
    • Semantic Web: Key to Solving Business Challenges
  • Case Study: MyFoodAlerts.com

Module 6: Service Composition & Business Process

  • What is a Business Process?
  • The Automation Paradox
  • Problems with Traditional BPM Tooling
  • Business Process the Enterprise Application Way
  • Business Process the Service-Oriented Way
  • Service-Oriented Process
  • Process Definitions
  • Example: Orchestration vs. Choreography
  • What is the Sweet Spot for Service Composition?
  • SOA Composite Application Example
  • Enterprise Applications and Process
  • Example: SAP NetWeaver
  • Transactions and SOA
    • Compensating Transactions
    • Transactions in the Cloud
    • Partition Tolerance
    • BASE instead of ACID

     

  • Case Study: SOA Journey at BP

Module 7: Web Services-Based SOA

  • Confusing SOA & Web Services
  • If not Web Services, Then What?
  • WSDL: Service Contract Starting Point
    • WSDL Basics
    • Concrete Description
    • Abstract Description
    • RPC vs. Document Style
    • Vendor Bozo Filter

     

  • Contract Metadata Beyond WSDL
  • What’s Missing from WSDL?
  • Sample Service Contract Template
  • OASIS Web Services Interoperability Organization (WS-I)
  • SOAP: Verbose Message Transport
  • What is a Policy?
    • Policy “Math”
    • Computing Effective Policy
    • WS-Policy Example
      • WS-PolicyAttachment
      • Policy Attachment to WSDL 1.1
      • Some Policy Standards
      • WS-SecurityPolicy Example (Policy & Conforming Message)

 

  • Physical Service Architecture
  • Three Approaches to State
  • Web Services Orchestration
    • BPEL Example
    • Limitations of BPEL
    • Thread-Based Execution
    • Queue-Based Execution
    • BPMN to the Rescue?
    • BPMN Example
    • Limitations of BPMN
    • How SOA Fills the Gap
    • What about Workflow?
    • Workflow & Web Services

     

  • What’s the Deal with UDDI?

Exercise: Service ContractHomework: Service CompositionsClass Ends at 5:00 PM

Day Three

Class Begins at 8:30 AM

Module 8: REST-Based SOA

  • Definition of REST
  • Dogmatic REST
  • REST Myths
  • Essential REST Terminology
    • What is a Resource?
    • Uniform Interface
    • PUT vs. POST: Initializing a Resource
    • What is a Uniform Resource Identifier (URI)?
    • RESTful vs. RPC-based URIs
    • What is a Representation?
    • Negotiating Representation Type
    • Content Negotiation
    • What is Hypermedia?

     

  • Four Architectural Constraints
    • Separation of Resource from Representation
    • Manipulation of Resources by Representations
    • Self-Descriptive Messages
    • Hypermedia as the Engine of Application State
    • HATEOAS Example
    • HATEOAS and URIs

     

  • State Transitions in REST
  • Custom Media Types
  • Contracted Services
  • Contract Metadata for REST
  • Intermediaries & REST
    • REST Starting Point
    • Caching Options
    • Proxy Pattern
    • Gateway (Reverse Proxy) Pattern
    • Asynchronous REST

     

  • REST Compositions
    • REST-Based Orchestration
    • REST-Based Choreography
    • Choreographing Orchestrations
    • Composite Representations vs. Composite RESTful Services
    • Everything is a Resource
    • Examples of Process Representations
    • Example of REST Choreography
    • Follow Links to Learn About Processes
    • Some Benefits of REST-Based BPM

     

  • REST-Based SOA
    • Essential REST-Based SOA Policies
    • Differences Between Web Services-Based SOA & REST-Based SOA

Module 9: Architecting with the Cloud

  • Essential Cloud Characteristics
  • Cloud Service Models
  • Cloud Deployment Models
  • Managed Hosting vs. Cloud Computing
  • Vendor Spin
    • Oracle’s Shopping List
    • IBM’s Shopping List
    • Cutting Through the Hype
  • Cloud Computing Roadmap
  • EA Cloud Strategy
  • Cloud Deployment Choices
  • Case Study: reddit Conde Nast

Module 10: SOA & Cloud Security

  • Critical SOA Challenge: Security
  • Security Fundamentals
  • The Context of IT Security
  • XML Threat Prevention
  • Mitigating XML Threats
  • Web Services Security
  • WS-Security Tokens
    • Security Assertion Markup Language (SAML)
    • SAML Assertions
    • Federated Security

     

  • Message-Level Security: Is SSL Sufficient?
  • Core Requirements for Securing Services
  • Cloud Security
    • The Three Core Cloud Access Control Concerns
    • Cloud Authentication: Federated Identity Management
    • oAuth as Federated Authentication Mechanism
    • Cloud Security: Authorization
    • Cloud Security: Policy
    • Cloud Security: Provisioning
    • The Big Picture: Retaining Control
    • Cloud Security: Data Confidentiality
    • Data Confidentiality in Motion
    • Key Management is “Key”
    • Alternative Approaches to Data Confidentiality
    • Know Your Data: Data Lineage & Provenance
    • Data Remanence
    • Cloud Security: Data Availability

     

  • Case Study: US Department of Defense OneStop

Module 11: SOA Governance

  • The Need for Governance
  • What is Organizational Governance?
  • How to Tackle Governance
  • The Cornerstone of IT Governance is Architecture
  • Elements of IT Governance Strategy
  • What is SOA Governance?
    • SOA Governance “in the Narrow”
    • SOA Governance “In the Broad”
    • SOA Governance Activities

     

  • Policies
    • Policy: Business vs. Technical Examples
    • Design Time Policy Examples
    • Run Time Policy Examples
    • Change Time Policy Examples
  • The Challenge of Policy Automation
    • Steps for Automating Policies
    • Supporting Policy Changes
    • Decoupling Policies from Services
    • Policy Management & Enforcement
  • Creating the Governance Framework
  • Governance Challenges
    • Governance Challenge: Reuse = Sharing
    • Publishing & Discovery Governance
    • Is Reuse a Real SOA Benefit?
    • Governance Pitfall: Versioning
    • Handling Service Versioning
    • Versioning Concepts
    • Versioning Strategies
    • Strict Versioning
    • Flexible Versioning
    • Loose Versioning
    • Versioning Policy Issues
    • Challenge: The Right Amount of Governance

Exercise: Governance FrameworkHomework: SOA Business CaseClass Ends at 5:00 PM

Day Four

Class Begins at 8:30 AM

Module 12: Cloud Governance & SOA Governance Infrastructure

  • Cloud Governance
    • Some Cloud Realities
    • Cloud Governance Challenges
    • Governance-Related Cloud Issues
    • Extending SOA Governance to the Cloud
    • Dealing with Cloud Reliability Example: Amazon EC2
    • Cloud Governance as VM Governance
    • Rogue Clouds
    • Cloud Governance: Auditing
    • Strategies for Dealing with Cloud Audit
    • More Cloud Governance Pitfalls
    • Cloud Governance: Run Time Considerations
    • Legal Issues
    • Cloud Availability & Failover
    • Cloud Governance Checklist
  • SOA Governance Infrastructure
    • Complexities of SOA Governance Marketplace
    • What is a Registry?
    • What is a Repository?
    • The Registry/Repository
    • Management & Loose Coupling
    • SOA Management: Many Facets
    • The Problem with SOA Management
    • The SOA Management Conundrum
    • SOA Monitoring & Management
    • Continuous Quality Activities
    • The First Rule of SOA Management
    • ZapElectric Physical Architecture Model
  • Case Study: SOA Organizational Change & Funding @ Novartis

Module 13: Planning & Running the SOA Initiative

  • How Do You Eat an Elephant?
  • Iterative: More than Step-by-Step
  • Iterate your Architecture?
  • Project Management for a SOA Project
  • Defining SOA Roadmap
  • Initial Assessments
  • Building Support for SOA
  • Building the SOA Business Case
  • Milestone / KPI Plan
  • The SOA Roadmap
    • The ZapThink SOA Roadmap
    • ZapElectric SOA Roadmap

     

  • SOA Maturity Models
    • Analogous to CMMI
    • SOA Maturity Model Pointers
    • Using a SOA Maturity Model
    • SOA Maturity Model: HP
    • SOA Maturity Model: Wipro
    • Open Group Service Integration Maturity Model (OSIMM), from IBM
    • “SOA” Maturity Model: Sonic/Systinet
    • SOA Maturity Model: Oracle
    • SOA Maturity Model: Software AG
  • Define Initial Iteration
  • SOA Pilots
  • Implementation Planning
  • Service Identification: Top Down vs. Bottom Up
  • Defining Services
    • Performance: Chasing the Bottleneck
    • Implementing Services: Methodologies for change
    • The Dual Lifecycle
    • The Service Lifecycle
    • Advanced Vision for Application Assembly
    • Where’s the code?
    • The Agile SOA Lifecycle

     

  • Top-Down: Analyze Processes
    • Process Analysis
    • Process Optimization
    • Discovering Existing Processes
    • Service Identification: Process Decomposition

     

  • Implementing Services
  • Defining New Compositions
  • Technology Selection
    • ZapElectric Component Model
    • Purchasing SOA Technology
    • Technology Selection: Choices

Exercise: SOA RoadmapFinal Exam: SOA Jeopardy!Class Ends at 3:00 PM

REGISTER


Venue:

 

Dovèl Technologies, Inc.
7918 Jones Branch Drive
Suite 100
McLean, VA 22102

REGISTER

Discussion

No comments for “LZA SOA & Cloud Training & Certification: DC – April 9-12, 2012”

Post a comment

FREE POSTERS

ZapThink's Vision for Enterprise IT in 2020
Featuring the five Super-Trends and three themes that will change the face of IT in the next decade.
Click here to download for FREE
10-pack of prints for just $29.95*

SOA Implementation Roadmap
Over 100,000 downloaded!
Click here to download for FREE
10-pack of prints for just $29.95*