Blog

So you have your killer erlang application that possibly could make you millions, but it was written in a test environment. Shoot, how do you change that “on the fly” at the application runtime? There are a many different ways this can be accomplished. This post will go over the basics of this typical issue.

There are a bunch of different ways to get connected to RabbitMQ. Thankfully the community has somewhat rallied behind the queue messaging system and there are a growing number of clients/libraries to aid in accessing the queue’s functionality.

In this post, we’ll explore the different options for connecting a ruby program to the AMQP-driven queue server. So, with no further ado:

Recently, I used Mochiweb for several projects (Alice) I’ve been working on. After some investigation of the current erlang web frameworks, Mochiweb suited our needs well. It’s lightweight, fast, open-source and pretty source code. Throughout this post, we’ll build a little mochiweb application, so note that it will be available in full for download at the end of the article, but we’ll write bits and pieces at a time.

So with no further ado:

Using mochiweb in erlang

Alice

http://alicetheapp.com.

As a queue server, RabbitMQ is super cool, but my company is hesitant to use it without a nice front-end or access to statistics about the server. So we set out to develop the latest RabbitMQ REST interface, Alice.

Update (01/04/2010): Added a github repos with a project template for starting new projects here: http://github.com/auser/erlproject_template.

The Rakefile in a ruby project is almost just as important as the code itself. Ask any rubyish to show you their project and you can bet your bottom dollar that nine out of every 10 projects of theirs has a Rakefile (most of the time, it’s 10/10). This is one thing that can make starting an erlang project painful… the Makefile (bum bum buuuummmm). Today, I’ll share a Makefile (for my own future reference too!) that works really well for me and my projects.