The Mojo homepage does a good job of pointing out some of the highlights, and linking to others.

• An amazing real-time web framework, allowing you to easily grow single file prototypes into well-structured MVC web applications.
  • Everything you need to build cloud-native web applications for state of the art container environments.
  • Powerful out of the box with RESTful routes, plugins, commands, Perl-ish templates, content negotiation, session management, form validation, testing framework, static file server, CGI/PSGI detection, first class Unicode support and much more for you to discover.
• A powerful web development toolkit, that you can use for all kinds of applications, independently of the web framework.
  • Full stack HTTP and WebSocket client/server implementation with IPv6, TLS, SNI, IDNA, HTTP/SOCKS5 proxy, UNIX domain socket, Comet (long polling), Promises/A+, async/await, keep-alive, connection pooling, timeout, cookie, multipart and gzip compression support.
  • Built-in non-blocking I/O web server, supporting multiple event loops as well as optional pre-forking and hot deployment, perfect for building highly scalable web services.
  • JSON and HTML/XML parser with CSS selector support.
• Very clean, portable and object-oriented pure-Perl API with no hidden magic and no requirements besides Perl 5.26.0 (versions as old as 5.16.0 can be used too, but may require additional CPAN modules to be installed)
• Fresh code based upon years of experience developing Catalyst, free and open source.
• Hundreds of 3rd party extensions and high quality spin-off projects like the Minion job queue.

Recent examples here using Mojo and its components include Apache Pulsar modules (Super Search for more), things like Minion are very powerful (see REST API with SFTP Pooling for a recent example use case). You personally may have no need for any of this, but rolling your own framework us unlikely to be as scalable or easily adoptable for others, which is important given the context of the discussion.

---

---

Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!

Titles consisting of a single word are discouraged, and in most cases are disallowed outright.

Read Where should I post X? if you're not absolutely sure you're posting in the right place.

Please read these before you post! —

• How do I compose an effective node title?
• How do I post a question effectively?
• Markup in the Monastery

Posts may use any of the Perl Monks Approved HTML tags:

a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr

You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)

	For:		Use:
	&		&
	<		&lt;
	>		&gt;
	[		&#91;
	]		&#93;

Link using PerlMonks shortcuts! What shortcuts can I use for linking?

See Writeup Formatting Tips and other pages linked from there for more info.