At AudioBox (https://audiobox.fm)
we have a strong use case for it.
We are already providing our users a "live filesystem" with Box, exciting that Dropbox is also adding this.
Domains are 0.10 specific I believe, and 0.10 is still bugged in few areas. I'd stay on 0.8.23 for quite some time since we are talking about stability.
It is large, but doesn't use any streaming or piping. As for remote services, just a bunch of remote APIs, and they work fine.
With the changes to streams in 0.10, I can understand it having some issues. That slipped my mind... but I don't do much streaming so I just assumed it worked.
Our beta is actually coming this weekend, our alpha is live currently though. http://alpha.soundkeep.com. It works great for us because we can keep server memory low since we can process and transcode audio as it passes through our server without having to buffer the entire file at once.
It works for us, but it comes with a lot of issues, some of which are pretty major, although this holds more true in the ecosystem, not always in core.
Problem is see is that no one seems to know how to solve them (it's a callback, no it's node, no it's v8), takes so much time or just plain don't care (socket.io, I'm looking at you), so you're on your own if you encounter something critical.
Either case start getting traction, don't over optimize at the start and watch out for memory leaks: there are tiny bits of best practices that you must follow (always consume the response? check. close the request appropriately? check. don't crash the whole node process? check.), some of which not really well documented, that can ruin your day should you get some important press and are not implemented correctly.
Take a look at the issue tracker of the libraries you are going to use, check if there's something that can affect you and perhaps contribute back!
>As can be read in the Olympic Charter, the Olympic symbol represents the union of the five regions of the world and the meeting of athletes from throughout the world at the Olympic Games. However, no continent is represented by any specific ring. Prior to 1951, the official handbook stated that each colour corresponded to a particular continent: blue for Europe, yellow for Asia, black for Africa, green for Australia and Oceania and red for America (North and South considered as a single continent); this was removed because there was no evidence that Coubertin had intended it (the quote above was probably an afterthought).
If you stop to think about it for a moment, if that were the case, it would make the olympic logo seem quite racist.
We'll have a look at this after our next release.