AWebFactory
Multi Tier Architecture

Home Page |

What most concerns us here is the separation of a system into three or more self-contained modules (above and beyond whether they are running on the same deployment node or not) isolating:

• Business logic
  (process logic that respond to requests and other stimulii)
• Persistent data
  (what (hopefully) stays there when the lights go out)
• Data access
  (different methods persistent data can be accessed)
• User interface
  (permitting (human and non-human) actors to interact with the system)

Clearly, and this is an issue we will have to work out with Ruby On Rails itself, the MVC pattern is clearly an oversimplification of “three-tiered” and multitiered architecture. At the end of the day, this is something we shall have to deal with.

From Wikipedia article Three-tier:

“Three-tier is a client-server architecture in which the user interface, functional process logic (“business rules”), data storage and data access are developed and maintained as independent modules, most often on separate platforms. The term “three-tier” or “three-layer”, as well as the concept of multitier architectures, seems to have originated within Rational Software.”

See also Wikipedia article Multitier architecture.

Content Victor Kane (ProjectMaster) and awebfactory.com.ar
Email me at info at awebfactory dot com dot ar
Full content (RSS 2.0) and Headlines (RSS 2.0)