Enterprise Integration Patterns: Introduction to Messaging
Meeting Room 12
Monday, 8:30, half day | 7 | · | 8 | · | 9 | · | 10 | · | 11 | · | 12 | · | 13 | · | 14 | · | 15 | · | 16 | · | 17 | · | 18 | · | 19 | · | 20 | · | 21 |
Bobby Woolf, IBM Corp.: I'm a co-author of Enterprise Integration Patterns and a co-author of The Design Patterns Smalltalk Companion, both from Addison-Wesley. I've presented popular tutorials at a handful of past OOPSLA conferences, including OOPSLAs 2002 and 2003; I've also presented at Smalltalk Solutions and JavaEdge.
Tutorial number: 22
It's no longer enough to be able to develop fantastic
applications; now they have to be able to coordinate
with each other as well. Messaging is in many ways the
most powerful yet least understood option available
for integrating applications. Literature on messaging
tends to be either very high-level, or API- or
product-specific, not practical advice on how to
develop messaging solutions.
This tutorial teaches application developers how to
use messaging to integrate applications effectively by
presenting a set of patterns—easily reusable best
practices that have been proven over time in a variety
of integration projects. The patterns are technology
and vendor neutral—they apply to APIs like the
Java Message Service (JMS) and the .NET
System.Messaging library, and products like IBM's
WebSphere MQ, Microsoft's MSMQ, and TIBCO Enterprise
Message Service. These patterns will teach you how
messaging works and how to use message-based
communication successfully.
This tutorial is based on the book Enterprise
Integration Patterns (Addison-Wesley, 2003). This
tutorial also serves as an introduction for OOPSLA
tutorial #31, "Enterprise Integration Patterns:
Designing Successful Integration Solutions."
Intermediate: This tutorial is intended for experienced application
developers who know an object-oriented language. No
messaging experience is required.
|
