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

In reply to Re: Nirvana through the templating yin yang (TT2 / CGI.pm) by chunlou
in thread Nirvana through the templating yin yang (TT2 / CGI.pm) by Aristotle

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":


  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.