In the last episode, you saw the basics of getting Keen.io up and running to track downloads for the media service.
In spite of the success in getting it to work, there's some potential drawbacks to having this solution hard coded into your router. What happens if Keen.io goes down or you have a network hiccup between your service and them? How do you handle crashes? And what do you do when you need to grow the code for Keen, but you don't want to make the router file ugly?
In this episode, you'll see the start of how to solve these problems and more, with the use of RabbitMQ to host a background analytics process.
While this episode doesn't cover the core of RabbitMQ (see the RabbitMQ For Node series, for that), it will show you just how easy it is to get RabbitMQ integrated into an existing solution, to keep your code clean.