Why Study Architecture First?

Posted by Jeremy Voorhis Thu, 02 Nov 2006 16:36:00 GMT

In my workshop, Understanding Web Architecture Through Ruby on Rails, I will delve straight into web architecture before discussing Rails at all. Here are 5 reasons why:

You should study web architecture if you want to…
  1. get a fresh perspective on Rails, and a better understanding of how the components of the model-view-controller pattern can fit together in a web framework.
  2. strive for coherence and good style at all levels of your application.
  3. share meaning with your users by exposing your domain model clearly to your users.
  4. learn how to take advantage of HTTP’s functionality and semantics, without spending days combing over RFCs.
  5. make applications that are available to agents other than web browsers, like feed readers or 3rd party apps, without duplicating code.

Comments

  1. Chris said about 6 hours later:

    Hello, I find your reasons very salient. Could you expand more on number 3 (perhaps an example)? Thanks.

  2. JV said about 8 hours later:

    @Chris:

    Sure. The Domain Model pattern has gotten a lot of attention lately as tools like ActiveRecord become more popular. The principles of the Domain Model, however, needn’t be restricted to classes in our applications’ domain layer. I am suggest that the Domain pattern can be applied successfully at a higher level when creating web resources. Concepts such as containment through has-many relationships, for example, can be expressed through the structure we choose for our resources’ urls.

(leave url/email »)