Menu

Posts written by Michael Bridgen

London Realtime hackweekend

April 17, 2012 by Michael Bridgen

Over the weekend, RabbitMQ co-sponsored London Realtime, two nights and two days of unadulterated hackery. It was all put on by the apparently indefatigable* crew at GoSquared, a very impressive debut effort.

As a co-sponsor we had one of the iPad prizes to award. We decided to allow hacks that used one or more of RabbitMQ, SockJS, or Cloud Foundry. This meant that about half of the twenty-seven hacks were eligible when it came to judging, making the choice rather difficult.

Read More...

PubSub huddle

September 16, 2011 by Michael Bridgen

All of a sudden there’s just one week to go until the PubSub huddle. It’s a one day conference, in London, about messaging. Not just RabbitMQ, but ZeroMQ, MQTT, XMPP and PuSH.

Read More...

Using the RabbitMQ service on Cloud Foundry with Node.JS

August 16, 2011 by Michael Bridgen

Recently we launched a RabbitMQ service for Cloud Foundry, making it simple to spin up a message broker to use with your apps on Cloud Foundry. There are tutorials online for using it with Ruby on Rails and with Java apps using Spring. Here we are going to look at using the RabbitMQ service with Node.JS apps.

Read More...

ZeroMQ =/= Erlang

June 30, 2011 by Michael Bridgen

Recently I saw a tweet saying “ZeroMQ Erlangizes everything!” or some such. While I realise that not everything posted on the web is meant seriously, it does seem there is a stream of similar claims lately that ought to be dammed.

In the article Multi-threading Magic1, Pieter Hintjens and Martin Sustrik persuasively explain why concurrency is better served by message-passing than by locks and shared memory. And they are fair, I think, in their analysis – except for the insinuation that using ZeroMQ transforms your chosen programming language into a domestic Erlang.

Read More...

AMQP 1.0 prototyping

December 1, 2010 by Michael Bridgen
We have been prototyping support for a new protocol, as is our wont. This one is called “AMQP 1.0 R0”, and it is the new issue from the AMQP working group (of which RabbitMQ, and latterly VMware, are a member). The “R0” indicates that it’s the first revision of a recommendation. The specification is incomplete: there are many TODOs, and to a large extent it is unproven. Those two facts are part of what prompted this prototyping.
Read More...

rabbitmq + node.js = rabbit.js

November 12, 2010 by Michael Bridgen
For those who have been away from the internets, node.js is an evented JavaScript engine based on Google’s V8. Because it is essentially one big, efficient event loop, it’s a natural fit for programs that shuffle data backwards and forwards with little state in-between. And it’s fun to program, an opinion apparently lots of people share, because there have been loads of libraries crop up around it. Among the more impressive of these libraries is Socket.
Read More...

Prompt-a-licious

October 2, 2010 by Michael Bridgen

I am setting up my old MacBook, reclaimed from my housemate, to be usable for the programmings.

Read More...

Well, I'll let you go ... basic.reject in RabbitMQ

August 3, 2010 by Michael Bridgen

Support for AMQP’s basic.reject just landed on default. It’s taken this long because we couldn’t agree on a single set of semantics that followed the specification, was actually useful, and wasn’t too complicated to implement.

Read More...