Stories
Slash Boxes
Comments
NOTE: use Perl; is on undef hiatus. You can read content, but you can't post it. More info will be forthcoming forthcomingly.

All the Perl that's Practical to Extract and Report

The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
 Full
 Abbreviated
 Hidden
More | Login | Reply
Loading... please wait.
  • Load balancing and fault-tolerence are fairly easy to code into a decent enterprise perl application.

    It could mean anything from sharing user sessions between servers or using a reverse-proxy direct traffic accross mutiple application servers and cache responses to slow connections, etc.

    Plucking a figure out of the air, 99% of load balancing and fault tolerence is done with the web servers, database servers & connections, and network design.

    There are modules and tools that allow you to integrate this into a perl application, but they are infrastructure issue - using 'Java' won't give you load balancing and fault-tolerence -- buying a million quids worth of Cisco networking, Sun server, IBM software, multiple Point-of-presence hosting and finally a J2EE server that can utilise all the services of everything else might, but only if you design it and ensure the application works with it all. You can do that with Perl too, but there will be less buzzwords and salesmen involved.

    --

    @JAPH = qw(Hacker Perl Another Just);
    print reverse @JAPH;