I think a lot of people jump on NoSQL solutions when scale out isn't needed because of the permeating "do everything in the application / client" mentality these days.
I work for LoopBack. The purpose of LoopBack is to help you develop and consume APIs. Here is a list of differentiating features:
1. A lot of connectors to backend systems, including an ORM for most of the popular databases, REST/SOAP apis, and other services such as storage and push notification. We want to make the integrations simpler for API developers.
2. Metadata based REST API programming. Write your business functions in plain JS and we'll expose them as REST APIs.
3. Swagger based API explorer that let you see and invoke APIs as you develop them.
4. Built-in user management, declarative ACLs and oAuth 2.0 provider to secure your APIs
5. Client SDKs (JS, Angular, iOS, Android) to help you consume APIs.
6. Strong tooling, including Yeoman based CLI tools and Web based StrongLoop Arc.
Full disclosure: I work for StrongLoop and am part of the LB team as a product manager among other things. Check us out - http://loopback.io/. Think Express (it's built on top of it) but with all the bells and whistles to help you with model driven development for APIs to power next-gen web, mobile, S2D IoT, etc. Don't take my word for it - check out our growing community - https://groups.google.com/forum/?fromgroups#!forum/loopbackj....
Well, as a LoopBack developer, I am biased, but I don't think LoopBack is just yet another framework. There are already some big names already using our framework, for example GoDaddy or Bank of America. You can find more names here: http://loopback.io/users/