What happens to a company when a visionary CEO is gone? Most often innovation dies and the company coasts for years on momentum and its brand. Rarely does it regain its former glory. Here’s why. Mi…
I have written an article about “Computing History: MapReduce in the 20th century”, which is now online at http://abarbanell.github.io/algorithms/2014/12/27/computing-history-mapreduce-in-the-20th-century/. In this text I show some computing history memories about the early days of MapReduce in an application in the 1990’s. Have fun!
Read more at my new blog here: http://abarbanell.github.io/jekyll/2014/09/27/moving-my-blog-from-wordpress-to-jekyll-bootstrap/
A small explanation why I now give Jekyll a preference over wordpress.
Here is a short description how to get RabbitMQ running on a Raspberry Pi.
- get a Raspberry Pi installed with Raspbian – just follow the standard installation guide from http://www.raspberrypi.org/downloads/
- get the rabbit MQ package from here: http://www.rabbitmq.com/install-debian.html
- I wanted to run a client in Node.js, so I got the latest node with these commands:
sudo dpkg -i node_latest_armhf.deb
- pick the node version of the RabbitMQ tutorials from here: https://github.com/squaremo/amqp.node/tree/master/examples/tutorials
Here is how this looks in pictures:
And the results: If you let a publisher with a simple “hello world” message run in a loop for 1000 times and start a subscriber for this queue at the same time, you will see the 1000 messages flying through your little Rabbit Pi in about 13 seconds, more than 50 messages per second!
You will also notice that there is hardly any concurrency between the publisher and subscriber, so the messages only get consumed when the publisher gets idle. This is contrary to what I see on a desktop linux system where the subscriber always “wins” and keeps the queue empty, and the publisher is slowed down to the pace of the subscriber.
You probably do not want to push the little Raspberry to many messages per second, but it is nice to know that you can!
This is a great experience of node development: Visual Studio with Intellisense, Debugging and Profiling, et voilà: publishing from git to Azure!
It was pretty straightforward to get two devices (Keyboard and Mouse) paired with one Unifying Receiver under Ubuntu 13.10 – follow this link to see how it worked for me in less then 5 min.
Now, this is my first step in the Ruby world, so apologize if I am doing dumb things here.
On a Mac Ruby was preinstalled, but on Linux 13.10 I needed to do this before installing Jekyll.
$ sudo apt-get install ruby1.9.1
this installs a few things around ruby, but you also need:
$ sudo apt-get install rubygems1.9.1
this installs the gem processor, and we should all be set, then:
$ sudo gem install jekyll
tries to fetch a few things and then builds everything for jekyll.
Last step is to go to the directory of your jekyll project
$ jekyll serve
This fires up jekyll in a webserver on http://localhost:4000
Enough for today, stay tuned.