On Fri, 02 Jul 2010 23:00:48 +0530, Amit Saxena wrote: > On Fri, Jul 2, 2010 at 9:41 PM, Peter Scott <pe...@psdt.com> wrote: > >> On Fri, 02 Jul 2010 09:34:05 +0000, Amit Saxena wrote: >> > I have around 6+ years of IT experience as a software development >> > mailing in scripting technologies using perl. >> > >> > I want to become technical architect in perl. Please help me / >> > suggest me / guide me on how should I start. Also please tell me any >> > resources which could help me. >> >> I have been developing in Perl for 20 years and doing enterprise >> architecture for 10 years. But I have no idea what a "Perl architect" >> is. Please explain in more detail. >> >> -- >> Peter Scott >> http://www.perlmedic.com/ http://www.perldebugged.com/ >> http://www.informit.com/store/product.aspx?isbn=0137001274 >> http://www.oreillyschool.com/courses/perl1/ >> >> -- >> To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional >> commands, e-mail: beginners-h...@perl.org http://learn.perl.org/ >> >> >> > Hi Peter, > > Perl is my main skill and I wanted to learn how to design and develop > enterprise applications in Perl. Development is OK but how to design is > something I want to know. So far, I am only developing small application > components in Perl but now I want to learn how to design the "whole > system" and subsequently develop in Perl. > > I might have incorrectly stated the term "Perl architect" but I hope you > now have got the idea of what I want to now learn. If yes, then please > suggest.
To develop large-scale applications in Perl, you may need to use a framework such as POE or Catalyst depending on the type of application. You should certainly understand Moose and how to develop modules. Design patterns help, but read the Perl Design Patterns Wiki rather than the turgid book, since many of the archetypal design patterns exist solely to solve problems of strongly-typed languages that don't exist in Perl. Inter-application interfaces should not be language-specific. If you are developing a service-oriented architecture, for instance, you might specify a type of enterprise service bus, but the way applications talk to each other should be based on standard protocols and formats. Principles of system architecture are higher level than application language. Ditto for enterprise architecture. I prefer the Zachman framework for the latter. -- Peter Scott http://www.perlmedic.com/ http://www.perldebugged.com/ http://www.informit.com/store/product.aspx?isbn=0137001274 http://www.oreillyschool.com/courses/perl1/ -- To unsubscribe, e-mail: beginners-unsubscr...@perl.org For additional commands, e-mail: beginners-h...@perl.org http://learn.perl.org/
