Skip to main content

Mojolicious plus Redis equals RestMQ-pl

I'm playing with Mojolicious. One of the fun projects I want to implement is a perl version of RestMQ. It was the main reason that I used then I requested a CPAN id. One of my previous complaints was, and remains, that the Python and Ruby versions of this project look elegant and fun. (this also means that a lot of the code is hidden in either the framework or the language; which I hate).

I'll be posting and submitting this project eventually, however, in the meantime I had not been able to get things working properly. There was a timing issue with MojoX::Redis and Mojo. It was not working well at all. I read and read all of the docs over and over again. In fact I had abandoned MojoX::Redis altogether in order to try AnyEvent::Redis. (it also failed).

Finally I reread a page in minute detail. The first piece of example code looked more like a standalone snippet. Which did not make any sense in this context because it was supposed to be a MojoX::Redis implementation in Mojolicious. (The wiki has been wrong more than once before)

But then; there it was:
If you are planning to use MojoX::Redis in Mojolicious' daemon mode, create MojoX::Redis instance with ioloop attr:

my $redis = MojoX::Redis->new(ioloop => Mojo::IOLoop->new);

Once I add this to my code and then added the stop and start calls to my function:
post '/q/:queue' => sub {
my $self = shift;
my $result = undef;
my $queue = $self->param('queue');
my $value = $self->param('value');
if (! defined $queue) {
$self->app->log->debug('queue was not in the URL ('.$queue.')');
} else {
my $uuid = undef;
my $lkey = undef;
my $q1 = $queue . $QUEUE_SUFFIX;
my $q2 = $queue . $UUID_SUFFIX;
$redis->incr($q2 => sub{
my ($redis, $res) = @_;
$uuid = $res->[0];
$self->app->log->debug('the uuid is ('.($uuid||'undefined').')');
$lkey = $queue . ':' . $uuid;
$redis->execute("sadd" => [$QUEUESET, $q1]);
$redis->execute("set" => [$lkey, $value]);
$redis->execute("lpush" => [$q1, $lkey]);
$self->app->log->debug('the uuid q is ('.($q2||'undefined').')');
$self->render(text => '{ok, ' . $lkey . '}');

it worked great. I still do not think this code is sexy and it's no where near the appearance of the Python or Ruby code(I should probably remove the debug statements). But it works... and it seems to be pretty fast too.


  1. I think that using async Redis library in blocking application is just senselessly — it requires more code because of callbacks, and doesn't give you big advantages.

  2. Agreed. In my post I was writing about using it directly with Mojolicious... and yet there was very little doc that actually described the integration other than to say it was possible and the refs I mentioned.

    On the other-hand, while I agree that it's overkill for most flat blocking apps... as soon as you want to do any work in parallel it's probably hella cool. (not that I've ever had a use-case that would apply).

  3. [...] Technical Intuition tokens from my toolbox HomeAboutContactFollow MeManagement Reading ListReferencesResume RSS ← Mojolicious plus Redis equals RestMQ-pl [...]


Post a Comment

Popular posts from this blog

Entry level cost for CoreOS+Tectonic

CoreOS and Tectonic start their pricing at 10 servers. Managed CoreOS starts at $1000 per month for those first 10 servers and Tectonic is $5000 for the same 10 servers. Annualized that is $85K or at least one employee depending on your market. As a single employee company I'd rather hire the employee. Specially since I only have 3 servers.

The pricing is biased toward the largest servers with the largest capacities; my dual core 32GB i5 IntelNuc can never be mistaken for a 96-CPU dual or quad core DELL

If CoreOS does not figure out a different barrier of entry they are going to follow the Borland path to obscurity.

UPDATE 2017-10-30: With gratitude the CoreOS team has provided updated information on their pricing, however, I stand by my conclusion that the effective cost is lower when you deploy monster machines. The cost per node of my 1 CPU Intel NUC is the same as a 96 CPU server when you get beyond 10 nodes. I'll also reiterate that while my pricing notes are not currently…

eGalax touch on default Ubuntu 14.04.2 LTS

I have not had success with the touch drivers as yet.  The touch works and evtest also seems to report events, however, I have noticed that the button click is not working and no matter what I do xinput refuses to configure the buttons correctly.  When I downgraded to ubuntu 10.04 LTS everything sort of worked... there must have been something in the kermel as 10.04 was in the 2.6 kernel and 4.04 is in the 3.x branch.

One thing ... all of the documentation pointed to the wrong website or one in Taiwanese. I was finally able to locate the drivers again: (it would have been nice if they provided the install instructions in text rather than PDF)
Please open the document "EETI_eGTouch_Programming_Guide" under the Guide directory, and follow the Guidline to install driver.
download the appropriate versionunzip the fileread the programming manual And from that I'm distilling to the following: execute the answer all of the questio…

Prometheus vs Bosun

In conclusion... while Bosun(B) is still not the ideal monitoring system neither is Prometheus(P).


I am running Bosun in a Docker container hosted on CoreOS. Fleet service/unit files keep it running. However in once case I have experienced at least one severe crash as a result of a disk full condition. That it is implemented as part golang, java and python is an annoyance. The MIT license is about the only good thing.

I am trying to integrate Prometheus into my pipeline but losing steam fast. The Prometheus design seems to desire that you integrate your own cache inside your application and then allow the server to scrape the data, however, if the interval between scrapes is shorter than the longest transient session of your application then you need a gateway. A place to shuttle your data that will be a little more persistent.

(1) storing the data in my application might get me started more quickly
(2) getting the server to pull the data might be more secure
(3) using a push g…