Learn how to recognize and optimize the design patterns that occur when you develop composite applications.
Patterns of development
The idea that in development we are often solving similar problems in similar ways has achieved great traction. Beyond its original application to object-oriented programming, people have found that there are many environments in which it is fruitful to look at work done in terms of patterns; in other words, to come up with generic solutions to generic problems that have wide applications. Composite application design and development are no different, and in this article, we look at patterns that make sense in this respect.
To organize the material, we break the types of patterns into a few different categories:
- Patterns that define common types of components
- Patterns that define groups of components in terms of how they are laid out and how they interoperate
- Patterns of applications or overall design techniques that can be used to structure your entire composite application or suite of composite applications
To read the entire article, see Designing composite applications: Design patterns
on the developerWorks website.
This article is the third in a series of articles on composite applications being published on developerWorks® Lotus. See the previous developerWorks articles,"The Lead Manager application in IBM Lotus Notes V8: An Overview," "Designing composite applications: Component design," "Designing composite applications: Design patterns," "Designing composite applications: Unit testing," "Designing composite applications: Writing an Eclipse component for IBM Lotus Notes,"and "Designing composite applications: IBM Lotus Notes components"