Mojolicious is a good choice. I haven't used Dancer2, so if that style is more to your liking, either one would work.
Deployment with a modern PSGI-style framework like either one will be more interesting. You'll probably end up running a Perl webserver in its own process and configuring Apache/IIS/Nginx to proxy to the backend. This isn't as exciting as it sounds once you get it up and running, but it's a different execution model from the CGI fork-process-per-request model you were probably using.
The other interesting part is that both Dancer and Mojolicious (and most other modern web frameworks) separate "generate HTML/CSS/JS" from "handle incoming query and post data" from "look up data in the database". Back in the day we didn't do that much with CGI and it made a mess for larger applications. The framework will help you keep these concerns separate, manage sessions and login, and maintain persistent database connections. Your job is to manage the logical separation and connections between these various Model, View, and Controller layers. Essentially that means that the first thing you have to figure out is what these frameworks will call "routing", or mapping the URLs exposed in the web app to functions/methods in the Controller layers.
There's a little bit of stuff to learn, but that should give you a few hints in the right direction.
In reply to Re: Old guy...Looking for advise on web platform selection.
by chromatic
in thread Old guy...Looking for advise on web platform selection.
by RedJeep
| For: | Use: | ||
| & | & | ||
| < | < | ||
| > | > | ||
| [ | [ | ||
| ] | ] |