Perl Architectures

Anonymous Monk has asked for the wisdom of the Perl Monks concerning the following question:

Replies are listed 'Best First'.
Re: Perl Architectures by kennethk (Abbot) on Nov 30, 2009 at 21:38 UTC
It's not quite clear to me what you mean by "different Perl architectures" (Perl is the language, perl is the program), and the examples you give don't make things any more clear. mod_perl and FCGI are glue code for tying perl to a web server. Moose is a Perl module that lets you easily use object-oriented coding principles in Perl (see Moose::Manual). Template is a Perl module for text document templating, separating business logic and display logic (see Template::Manual::Intro). XS is a tool for interfacing Perl code with compiled code, usually C (see perlxstut). It would be quite possible for a single web application to use nearly every one of the technologies you've listed above (mod_perl and FCGI serve the same purpose). All of this and more info is available from Google, Wikipedia and CPAN with the keywords you've already listed. The only thing they have in common is they are ways of extending the functionality of the perl interpreter. If that's what you mean by architecture, then every Perl module ever developed is a "Perl architecture". What do you want to do with Perl? You're not going to want a circular saw if you are changing your oil.	[reply]
Re: Perl Architectures by cdarke (Prior) on Dec 01, 2009 at 11:22 UTC
Why? TMTOWTDI There are different ways of handling Perl because there are many different environments and ways of writing and running programs. One of Perl's strengths is its flexibility - it can be used almost anywhere. Another is that it does not dictate how you do things: that's up to you.	[reply]