comment on

There are basically two reasons to go with a .Net or J2EE solution

You have expertise in those architectures that you do not have in the 4GL languages, like Perl or Python.
You are already seriously committed to a Win32 architecture.
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?

Perl is developed faster
90% of every Perl application has already been written, tested, and deployed.
Perl is supported on (nearly) every single system known to man
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

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.


Clear questions and runnable code get the best and fastest answer
	PerlMonks