August 2003
Intermediate to advanced
624 pages
15h 3m
English
In this book I present two different implementations of our architecture. Why? Basically, for reasons of platform independence and portability. However, I'm also doing it out of a pragmatic recognition that there isn't just one dominant programming language, and I want to be able to speak to both camps.
We can use an analogy to home building in order to understand the two implementations of a single software architecture. The analogy isn't exact, but there are enough high-level similarities between building houses and building software to serve our purpose.
When an architect designs a house, he or she first establishes the number and types of rooms that the client wants as well as the general ...