Replacing RabbitMQ with nginx for inbound request routing
In a conversation on Twitter about most satisfying code cleanup, I mentioned the time that I completely replaced the agent-inbound HTTP routing at Electric Imp.
In a conversation on Twitter about most satisfying code cleanup, I mentioned the time that I completely replaced the agent-inbound HTTP routing at Electric Imp.
I’ve got an Electric Imp Environment Tail in my office. It monitors the temperature, humidity and pressure. Currently, to display a graph, it’s using flot.js and some shonky Javascript that I wrote. It remembers samples from the last 48 hours.
At Electric Imp (now part of Twilio), my team uses Erlang’s Common Test for driving our system tests. These are (almost-)end-to-end tests that exercise (almost) the whole platform.
I last posted on this topic about 4 years ago. It’s time for an update.
This question just came up on Twitter:
Originally posted, 16 June 2014, to the Electric Imp blog. Preserved here.
If you don’t know what electric imp is, what an April Development Board is, and you don’t have a Dymo LetraTag LT-100H label printer, then this isn’t going to be of much use to you.
I’ve been working for electric imp for about three months now, and I’ve been planning to articulate why I made the change, or more specifically, how it meant getting way out of my technical and working comfort zone.