A short summary of the patterns in Patterns of Enterprise Application Architecture (P of EAA).

joshua bloch

for n00bs like me

n the Java community there's been a rush of lightweight containers that help to assemble components from different projects into a cohesive application. Underlying these containers is a common pattern to how they perform the wiring, a concept they refer under the very generic name of "Inversion of Control". In this article I dig into how this pattern works, under the more specific name of "Dependency Injection", and contrast it with the Service Locator alternative. The choice between them is less important than the principle of separating configuration from use.

The Actor Model of Computation, as defined by Carl Hewitt [1] and elaborated by Gul Agha [2], defines three primitive operations. These operations are “Send”, “Create” and “Become”. The “Send” operation transmits an asynchronous message to a known receiver. The “Create” operation constructs a new actor with a specified initial behavior. The “Become” operation defines the behavior used to process the next message received by the current actor. We will examine each of these primitives, focusing on their relationship with various computational concepts. The actor model provides a compact mode of expression. By unpacking this model, we hope to better understand how to take advantage of its power and elegance.

This site's primary focus is PeopleProjectsAndPatterns in SoftwareDevelopment. However, it is more than just an InformalHistoryOfProgrammingIdeas. It started there, but the theme has created a culture and DramaticIdentity all its own. All Wiki content is WorkInProgress. Most of all, this is a forum where people share ideas! It changes as people come and go. Much of the information here is subjective. If you are looking for a dedicated reference site, try WikiPedia; WikiIsNotWikipedia!