That's why I thought about using an HDD. How does it need to be plugged, on th GPIO ports ?
This would be a good idea for a node in the past but not so much now, mainly due to the blockchain size and it's efficiency. The mempool was much slower in the past with lower transaction volume and hence it could run with lower ram and more connections. With the increased mempool, you would need to tweak the client slightly by using several optimizations. As shorena said, consider verifying the entire blockchain on your own computer before moving it to the raspberry pi. By copying the entire directory, you won't have to synchronize and verify from the beginning.
http://www.electronicsweekly.com/blogs/distribution-world/microsoft-starts-selling-raspberry-pi-2016-01/
not that I would suggest using Windows 10.
Than you for your advice. So you would recommend to use a Linux computer instead of a Raspberry Pi 2. And what about a cluster of RPi 2 ? This way the RAM and the CPU capacities could be increased in keeping the bill low.
I've never heard of someone daisy chaining raspberry pis to run a Bitcoin node. Daisy chaining[1] is sure possible but it isn't for an average users. If you're thinking about daisy chaining raspberry pis, it makes more sense to buy an old low profile computer to run the node on.
[1] http://www.zdnet.com/article/build-your-own-supercomputer-out-of-raspberry-pi-boards/
What frightens me in the "old low profile computer" is that, since is old, he can "die", especially his HDD. I know that I might change it, but this way I prefer buy a new computer, since the price difference will be really low, and this lead to a big bill, so I want to build it on a (few) Raspberry Pi 2(s), so the cycle restart ...