comment on

Unless you have already done so, you will need to hire people with the following skillsets:

DBA
Sysadmin

Unless you have personally been a DBA or sysadmin on a large project, you will mess it up. This isn't optional. There are a number of critical FAIL-if-you-don't-take-into-account considerations that a programmer will never think of, because that's not their job. I am both a programmer and a DBA, but I'm not a sysadmin, so I make sure I have a list of very good sysadmins I can call when I need to. Just as I'm on that list of DBAs for many monks. Unless you have done this, everything else is completely and utterly worthless.

I'm saying that as someone who's been DBA and developer on a number of large web applications written in Perl using a MySQL backend. If you would like some further advice on the matter, feel free to contact me either here on at rkinyon@cpan.org

Beyond that, it's the basics. Pick a web framework, an ORM, webserver, and application server. I personally prefer Catalyst, DBIx::Class, Apache, and FCGI. I know smart people who like Jifty, Jifty, Apache, and mod_perl. There's a number of choices. The key is to pick one and learn it inside and out.

As for laying out the app, screw the documentation crap. Build it with tracer bullets and week-long deliverables. If you can't break a piece down to week-long chunks, look again.

My criteria for good software:

Does it work?
Can someone else come in, make a change, and be reasonably certain no bugs were introduced?

In reply to Re: Large Web Application Ponderings by dragonchild
in thread Large Web Application Ponderings by stonecolddevin

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.


Don't ask to ask, just ask
	PerlMonks