There are basically two reasons to go with a .Net or J2EE solution
  1. You have expertise in those architectures that you do not have in the 4GL languages, like Perl or Python.
  2. You are already seriously committed to a Win32 architecture.
  3. You already have a large codebase in those architectures.

For a completely new project, it often makes more sense to build it in Perl/PHP. Reasons?

  1. Perl is developed faster
  2. 90% of every Perl application has already been written, tested, and deployed.
  3. Perl is supported on (nearly) every single system known to man
  4. Perl has support for (nearly) every single data store known to man

As for the multi-tiered stuff ... I worked on an e-commerce site that had all the MVC architecture built. Oracle was on its own server, separate from the Apache servers. It was all in Perl.

I've also worked on another web app that had 4 front-end servers, using MySQL for session information. They communicated using Tuxedo across the DMZ to an Oracle server (with HA backup). All the SQL was in Pro*C in a bunch of C++ classes.

The point here is that Perl is a very effective language for every part of the web app. I've heard of apps that have their engine in Perl and use Java/.Net for the presentation layer. No problem!

------
We are the carpenters and bricklayers of the Information Age.

The idea is a little like C++ templates, except not quite so brain-meltingly complicated. -- TheDamian, Exegesis 6

... strings and arrays will suffice. As they are easily available as native data types in any sane language, ... - blokhead, speaking on evolutionary algorithms

Please remember that I'm crufty and crochety. All opinions are purely mine and all code is untested, unless otherwise specified.

In reply to Re: Multi tiered web applications in Perl by dragonchild
in thread Multi tiered web applications in Perl by pernod

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.