Here is a classic view of a layered approach to distributed computing also known as SOA (service oriented architecture). This loosely couple architecture routes all messages through a centralized bus or ESB (enterprise service bus).
An ESB (enterprise service bus) can best be explained by the PCI Local Bus analogy. Within a PC, the PCI bus is the centrally located component that all other devices interface with. The PCI bus creates a common way of communicating with various computer components and eliminates the need for each component to be hard wired to all other components. The ESB provides a standard interface for messaging within an architecture and is the centralized component for messaging, routing, and transformation.
This slide shows the IT roles within each layer of the architecture. This is not an exhaustive list but shows the need for specialized skills.
Slide used to explain to the business how we can build a composite UI that is driven by new business processes without blowing away years of legacy systems.
This picture explains the difference between internet enabled apps, cloud computing, and PaaS
Example of Data Services (Source: BEA)
SOA Security Challenges (Source: Forum Systems) www.unatekconference.com/images/pdfs/presentations/Yunus.pdf
Typical view of SOA
Creating a mashup by joining various data services and applying filters
Example of a simple mashup design
Mashup of Google Maps and Carpool info
In this example, Data Services allows developers to leverage a single view of customer data
Example of a Shopping Cart workflow diagram
jBoss SOA Stack
MuleSource SOA stack
WSO2 and others in a typical SOA stack
Hybrid of Cloud and On-Premise Architecture when data security is an issue.
Example of a business process integrated with a rules engine
Simple example of a business rule
