What architecture to use is often dictated by your organizational and development environment, besides your teammates' skills and the merit of the technology itself.

Whimsical development process encourages PHP type of technology, which more easily allows "on-the-fly" coding with little planning.

N-tier architecture (starting with your using templating, for instance) requires intellectual and procedural supports from both programmers and non-programmers.

The idea could be characterized in the following table, as an example (be the changes due to internal or external reasons):

		Architectural1. (Backend Logics) Changes
		Rare		Often
		Business Rules2. (Middle Layer Logics) Changes		Business Rules2. (Middle Layer Logics) Changes
		Rare	Often	Rare	Often
Presentation (Frontend Logics) Changes	Rare	Assembly? (just kidding)	Template + scripting lang.	(ever happened?)	Template + scripting lang.
	Often	Template + compiled codes	PHP	(not sure this can happen)	PHP (simple 2-tier) + yoga, aspirin, etc

^1. This usually means DB, XML, etc.
^2. This translates into Perl scripts, Java beans, COM, stored procedures etc. for most people

---

---

• Are you posting in the right place? Check out Where do I post X? to know for sure.
• Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:

  <code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>

• Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
• Want more info? How to link or How to display code and escape characters are good places to start.