ZapThink Licensed ZapThink Architect Renewal Course Version 10.0
Online, Self-Paced, Computer-Based Training Course.
Cost: US $795
This online course is for all Licensed ZapThink Architects who took the LZA course before January 2013.
Completing this course extends your LZA certification until a year after completion of the renewal course or a year after completion of your original LZA course, whichever is later.
Note: if you have already registered for this course, you can return to the login page for our online courses at http://learn.zapthink.com.
LZA Renewal Course 10.0
SOA as Agile Architecture
SOA: Work in Progress!
What is an Enterprise?
What all Enterprises Have in Common
What About Enterprise IT?
SOA is EA Architectural Style
The Myth of the “Final State”
Missing Link: Business Agility
The Promise of SOA
ZapThink’s Definition of SOA
How Does SOA Provide Business Agility?
Difference Between Traditional Integration & SOA
SOA Heralds New Approach to Architecture
Starting Point: (Traditional) Systems Engineering
Waterfall Software Project
Iterative/Agile Software Project
Not-So-Agile Updates to Existing Software
What Agile Software Should Really Look Like
Designing Beyond Use Cases
Where’s My Agility?
Agility as Emergent Property
What is an Emergent Property?
Introducing Complex Systems
Changing the Focus of Engineering
Complex Systems Engineering?
Architecting only the Technology is Insufficient
You Must Architect the People as Well!
The Missing Link: Governance
Governance: Architecting People
Next Generation Governance
APIs to Services: Past & Future
In the Beginning, The Application was the Program
Enter Distributed Computing
And with it, Client/Server Architectures
Next up: Add OO to the Mix
Problem: Tight Coupling
Enter Declarative Programming
Should Services Be Nouns or Verbs?
Web Services Initially followed RPC Style
Problems with RPC Style
Should Web Services be Declarative?
Document Style Web Services
Benefits of Document Style
Should All Interfaces Be Services?
Problems with Document Style Web Services
REST to the Rescue!
What is REST Anyway?
Is REST about APIs?
Essential REST Terminology
What is a Resource?
PUT vs. POST: Initializing a Resource
What is a Uniform Resource Identifier (URI)?
RESTful vs. RPC-based URIs
What is a Representation?
What are Hypermedia?
Four Architectural Constraints
Separation of Resource from Representation
Manipulation of Resources by Representations
Hypermedia as the Engine of Application State
Discoverability with REST
Discoverability & Hypermedia
Custom Media Types
Contract Metadata for REST
The REST Shell Game
Heavyweight vs. Lightweight SOA
Service Mediation with Oracle Service Bus
EDA without vs. with SOA
So, Where’s the State?
Web Services’ Achilles Heel
Threads & Queues
Physical Service Architecture
Fiorano Brokered Peer-to-Peer Architecture
HATEOAS in Action
Explicit State Transitions in REST
REST Starting Point
Gateway (Reverse Proxy) Pattern
RESTful State Management Essential for the Cloud
Scalability & State, The Old Way
Building Intermediary-Based SOA Infrastructure
Case Study: US Coast Guard SPEAR Architecture
Service Composition & Business Process
Composite RESTful Service
Everything is a Resource
Examples of Process Representations
Example of REST Choreography
Follow Links to Learn About Processes
Some Benefits of REST-Based BPM
The Role of Data & Semantics
Resource Description Framework (RDF)
RDF & Web Services
What About Custom Media Types?
Custom Media Types & HATEOAS
Custom Media Types & RDF
In Progress: HAL (Hypertext App Language)
Architecture-Driven Governance Maturity
Step 1: Human-Centric SOA Governance
Essential REST-Based SOA Policies
Step 2: Technology-Centric SOA Governance
Supporting Policy Changes
Dealing with Change
Avoiding Hall of Mirrors Problem
SOA Governance (Supposedly) Works this Way!
Step 3: Technology-Centric Architecture-Driven Governance
Securing RESTful Interactions
OAuth as Federated Authentication Mechanism
Is OAuth Doomed?
Step 4: Human-Centric Architecture-Driven Governance
Beyond SOA Governance