|The PEAK Developers' Center||FrontPage||RecentChanges||TitleIndex||WordIndex||SiteNavigation||HelpContents|
Note: when beginning to explore PEAK, the best order in which to explore the modules is: binding, config, naming. Read the interface files for those modules in that order.
The peak.model subsystem provides a framework for developing rich "domain models", the set of classes which represent the various entities in the problem domain of a given application. In PatternsOfEnterpriseApplicationArchitecture Martin Fowler describes the use of domain models as the most powerful of three core architectural design patterns. The pattern is also the most complex, but the flexibility and reusability gained are crucial for medium to large size applications.
The peak.binding subsystem provides a framework for developing applications as a hierarchy of interconnected component objects, using the InversionOfControl pattern. A variety of mechanisms are provided for component objects to find (or create) and make use of other component objects. These components may be as simple as a filename or other user-provided option, or a complex object such as a database connection. Through binding, any resource needed in more than one part of an application can be made available and "bound" by the component objects that need it.
To learn more about what a WikiWikiWeb is, read about WhyWikiWorks and the WikiNature. Also, consult the WikiWikiWebFaq.