Abstract Web Application Architecture
Independent of its specifics, an application architecture must be capable of capturing the business logic, data, interface, and network requirements just described. In fact, in describing a prototypical application architecture, it is best to start with a very general design. Then, progressively, we can fill in some of the details, such as where the Web server fits. The important thing here is to not get lost in specifics. Times will change, technology will change, but customer requirements, by and large, will remain constant.
From Client to Server: Thin and Fat Clients
Starting at the 10,000 foot level, Figure 2-1 shows the composition of a very abstract application. We see that the user directly interacts ...
Get Building Scalable and High-Performance Java™ Web Applications Using J2EE™ Technology now with the O’Reilly learning platform.
O’Reilly members experience books, live events, courses curated by job role, and more from O’Reilly and nearly 200 top publishers.
