I have many web-apps running online, and most are supported by a MySQL backend, with tables using the InnoDB engine.
InnoDB is great, it enforces data-integrity with foreign keys, not like MyISAM that doesn't give a damn.
If your web-apps are ever dealing with large data-sets or complicated translations of data, caching with memcached may provide a clean and effective solution to improving performance. Caching is the act of remembering things for later use, usually complicated objects that take a long time to prepare, but are needed regularly.
Complex websites have a tendency to be slow, and can give a horrible user-experience leaving your visitors waiting for pages to load.
To prevent this you need to look at all aspects of a website, and how it all hangs together, from the web-server, down to the very last pixel of an image.
Starting on a Commadore C64 in the mid-80's, Rob has been programming ever since, though thankfully the hardware has improved slightly.
After learning Basic, Visual Basic, Assembly, C, and C++, Rob eventually found himself needing to create a forum for a personal website; that's when he found Perl.
He's been developing in Perl for the past 10 years in various dev-manager roles. He has a few contributions on CPAN and works primarily with Plack and Catalyst, on a CentOS/MySQL stack.
He's always keen for his team(s) to understand where their applications are running, and what is going on outside the Perl-space they're familiar with.
This blog aims to cover the various technologies he's worked with over the years, and found useful to know about when working specifically on web-apps.