[jonaphin]

It seems that Go is fast, so if you expect a very high volume and want to keep the server bill low (I don't know about the developer cost comparison) it might be the way to go.

I've used Sails.js (built on top of Express.js) and can't say it's anywhere near Rails yet.

Also, Node maybe be the "wrong" tool for building APIs. By wrong I mean it's not its particular strength.

[justinzollars]

Why do you consider it wrong? It seemed almost ideal especially expressjs when breezing through the dev docs

[jonaphin]

As I said, I've used Sails.js. Their ORM is subpar, doesn't even support associations yet. By wrong I meant that where Node.js shines most is in its unified approach to client/server relationships. Since you're building an API (as in server-side logic with world-facing endpoints) you may want to stick to Rails, since it's great at that out-of-the-box, for tried-and-true.

[ricardobeat]

You can't judge the platform by one framework. Node.js also shines in concurrency and networking, which are valuable things for an API, and allows you to offer streaming endpoints with ease.