There are several types of architecture involved in a web app. Some of these are found in desktop apps, some are not.
Content Architecture – focuses on the definition of the overall hypermedia structure of the WebApp. Generally there are four main types of structures.
Linear structures follow a set path that the user should follow. Some my have optional pages, but it still follows a set path and the optional pages lead back to the main flow. (Think of them as side quests.)
Grid structures are an architectural option that you can apply when WebApp content can be organized categorically in two (or more) dimensions. For example, consider a situation in which an e-commerce site sells golf clubs. The horizontal dimension of the grid represents the type of club to be sold (e.g., woods, irons, wedges, putters). The vertical dimension represents the offerings provided by various golf club manufacturers.
Hierarchical structures are undoubtedly the most common WebApp architecture. Unlike the partitioned software hierarchies discussed.
A networked or “pure web” structure where architectural components (in this case, Web pages) are designed so that they may pass control (via hypertext links) to virtually every other component in the system. This approach allows considerable navigation flexibility, but at the same time, can be confusing to a user.
WebApp architecture describes an infrastructure that enables a Web-based system or application to achieve its business objectives.
MVC is one of the most common architectures, where you have a Model Viewer and Controller components. Think of it as a 3 tiered system.
The model (sometimes referred to as the “model object”) contains all application-specific content and processing logic, including all content objects, access to external data/information sources, and all processing functionality that is application specific. The view contains all interface-specific functions and enables the presentation of content and processing logic, including all content objects, access to external data/information sources, and all processing functionality required by the end user. The controller manages access to the model and the view and coordinates the flow of data between them.
Web App Architecture Design was originally found on Access 2 Learn
