Achieving True Asynchronous Database Queries in Mojolicious

The article introduces asynchronous database handling in Perl, noting that traditional Dancer frameworks struggle with full async support, while Mojolicious enables it easily after just a few days of experimentation.

It defines the ideal async scenario: a web page requiring five SQL queries, each taking one second, should still render in one second for any number of concurrent users on a single‑process worker.

Two async implementation methods are described:

Using multiple processes to simulate async by forking for each blocking query. This approach is clean and reliable but consumes significant server resources when many concurrent requests trigger many forks.

True socket‑level async leveraging database driver support (e.g., DBD::mysql's async features). This provides genuine non‑blocking I/O, though the data‑return phase remains effectively blocking; however, the author considers this negligible because the query execution time dominates.

The article then surveys several Perl async DB modules, illustrated with screenshots:

AnyEvent‑based modules (first‑type async) such as AnyEvent::DBI::MySQL and other AnyEvent wrappers.

Second‑type async modules that integrate directly with Mojo, including a high‑quality module the author currently uses, a Japanese experimental async library, and the underlying DB driver itself.

After a brief note on module selection (preferring AnyEvent::DBI::MySQL for its built‑in connection pooling), the author provides a practical tutorial on building a non‑blocking Mojo application.

Project Setup

Generate a full Mojo app with mojo generate app MyApp (similar to dancer -a). The generated lib/MyApp.pm contains a startup subroutine, which is the only place to inject the async DB connection.

Startup Function Example

The article includes an image of the complete startup function that registers the async DB handle.

Testing the Async Query

Run a simple SQL test like select now(), sleep(5) to verify that the request returns after roughly five seconds regardless of the number of concurrent browsers, instead of the cumulative 25‑second delay.

Launch the app with morbo or hypnotoad, then open multiple browsers or use ab to simulate concurrent users. All requests should complete in the same time as a single query.

The author apologizes for any language issues and notes limited time for polishing the article, inviting corrections.

Note: The content was originally posted on the ChinaUnix community; proper attribution is required for reuse.