Architecture and Design of Service-Oriented Systems (Part 1)

SOA is not an architecture. SOA is not a system. SOA is a way of designing systems, an approach to system development, an architectural style, a design paradigm.  As an architectural style, SOA can be described in terms of components and connectors. The main components are the services, service consumers, and SOA infrastructure. The connectors are predominantly message-based document exchanges. In essence, SOA is an architectural style and an approach to software development that goes with the style. You do not “build a SOA,” you “build a service-oriented system.”
The objective of this tutorial is to provide guidance on the architecture and design of service-oriented systems. In the first part of the tutorial, I will present and discuss basic concepts related to software architecture design and the impact of service orientation on system qualities. The second part will focus on SOA infrastructure-design considerations, decomposition of an enterprise service bus (ESB) into patterns and tactics as an example of SOA infrastructure, and principles of service design. The goal  is to provide a starting point for using quality attribute requirements to design infrastructure and services in a service-oriented system.
Part 2 of this tutorial will take place Wednesday, March 6. Pre-register here.

 If you have previously registered for this event, please login below:

Registration is required to attend this event. Please register now.
First Name*
Last Name*
Work Title*
You must have Javascript and Cookies enabled to access this webcast. Click here for Help.
Please enable Cookies in your browser before registering for the webcast.
*Denotes required.