Excellent article describing common design patterns used by frameworks, with examples and trade-offs/drawbacks discussed.

A framework is defined as "code that calls your (application) code". Not sure I totally agree, since frameworks that I've built are usually instantiated by the application explicitly. Well, that launch sequence is one of these patterns described.

Here's a table of contents.

- Callback function

- Subclassing

- interfaces

- imperative registration API

- convention over configuration

- metaclass based registration

- language integrated registration

- DSL-based declaration

- imperative declaration

- language integrated declaration

(Nitpick: might want to standardize the capitalization of titles, like "Pattern: Callback Function".)