Because the whole point of using websockets for me is to reduce latency. And I am guessing that polling the database all the time is computationally expensive.

What kind of latency are you looking for?

I doubt its expensive to query the database for messages since X ... once or three times a second ... "realtime" for humans :)

In truth, all "events" are actually just variations of polling with different softwares doing the polling (OS...)

See also Mojolicious: Websocket example under hypnotoad for similar discussion

So in that thread it used to be So there is the context, use Mojo::Redis - Asynchronous Redis client for Mojolicious. but its now deprecated with link to Mojo::Redis2 - Pure-Perl non-blocking I/O Redis driver ... redis ... The Publish/Subscribe feature is fully implemented, so a client of a slave may SUBSCRIBE to a channel and receive a full feed of messages PUBLISHed to the master, anywhere up the replication tree.