1、- 1 - 外文原文 Chapter 2. Architecture In theory there is no difference between theory and practice. But, in practice, there is. Jan L.A. van de Snepscheut Architectureits that level above design where we get our first glimpse of what the system will ultimately resemble, how it will be built, the vision
2、 of the application and system as a whole. By keeping the advice contained in the items that follow in mind when laying out the basic flow and design of your enterprise applications and systems, youll make progress toward a noble goal: establishing an architecture that enables a high-performance, hi
3、gh-scalability enterprise system. Item 1: Prefer components as the key element of development, deployment, and reuse One of the difficulties many Java developers face when attempting their first J2EE-based project is that J2EE applications are built differently than traditional Java applications: ra
4、ther than building applications, J2EE mandates the construction of components that plug in to an already-existing application, that being the J2EE container itself. This may not seem like a large difference at first, but its implications are huge, in two different directions. First of all, this means that developers arent really interested in constructing objects per se but in creating strongly encapsulated components that (in the case of J2EE) are made up of tightly coupled constituent obj
