LoopBack, a new Node.js framework by StrongLoop

Nitpick, but the "GET /people/{id}/exists" in the example to check if the instance exists is a bit weird, would suggest "HEAD /people/{id}" for this type of operation.

As someone that is in the middle of writing a nodejs thin API layer, working with express-resource, this looks really amazing to me. It looks like I can stop worrying about writing middle thin-API code, and focus on front-end manipulation of a stable middle&#x2F;backend<p>However, the scale of this really worries me. I really like small tools (flask over django, knockoutjs over angular sometimes,etc) -- and this seems like a LOT to take in to a project, sort of hoping it all just works...<p>Also, why is Postgres support not more prominently stated? It&#x27;s there, but I had to search for it. And on that note, why is JSON stored in postgres as a varchar? why not use the postgres JSON type (compatibility reasons, maybe?)

I feel like you should give a little shout out to the folks over at Wordnik <a href="https://github.com/wordnik/swagger-ui" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;wordnik&#x2F;swagger-ui</a> for putting together such an awesome API browser.

This looks amazing, and the StrongLoop team is chalked full of some great Node.js developers.<p>But for some reason I&#x27;m still worried about using it as the backbone for an enterprise scale application; it almost does too much. Perhaps I&#x27;m just too averse to this amount of &quot;magic&quot; in any piece of infrastructure due to my Django days.<p>The code is open, but you&#x27;re not just buying into a single module with a single purpose -- this is an entire architecture. I guess in such cases, worry is warranted before accepted it as the backbone of your company&#x2F;application.

Wow, I&#x27;m building something a bit similar in the Go area: <a href="https://github.com/sergiotapia/paprika" rel="nofollow">https:&#x2F;&#x2F;github.com&#x2F;sergiotapia&#x2F;paprika</a><p>Nice to know it&#x27;s a good idea that a lot of people will find useful. :) Granted in it&#x27;s current vision Paprika won&#x27;t handle authentication.<p>It&#x27;s basically an API server in-a-can. Defined your structs, set up your .toml database configuration and paprika.Start(&quot;3000&quot;) on a port.

Nice landing page, I&#x27;ll give them credit for that. But why would I want to use this instead of Express or Restler?

This is slick, especially the API explorer, but my biggest gripe about these orm&#x27;s is that once you get past the very basic CRUD, you need to execute custom sql.<p>Does it support custom DB types?<p>For example, I want my primary keys to be bigint on Mysql, and not have to override the underlying dbdriver to do the mapping. I&#x27;d prefer to set the appropriate dbtype in the model, and have the driver pass it along directly.<p>Also does it support dbdriver level SQL query execution?<p>I have custom aggregation query across a self join, and that&#x27;s not easily represented with static methods on a model.<p>Today I use node-orm2, with a custom SQL script that updates the identity columns to be bigints, and it supports executing raw sql queries (with some basic parameter sanitizing).

For node-based API backends, I&#x27;ve been using Sails.js or Deployd. In addition to providing automatic RESTful CRUD APIs for your data models, both Sails and Deployd also provide WebSocket interfaces that make it really easy to support real-time capabilities without doing any extra work. It doesn&#x27;t look like LoopBack does that.<p>I&#x27;ve been particularly happy with Sails.js as the backend framework for my single-page web apps. I get rid of the Sails view system and use it solely as an API backend. The current 0.10 beta, which adds support for associations in data models, is really nice.

Cool! Handling CRUD APIs and authentication desperately needs a flexible library! I can&#x27;t seem to find any kind of versioning, changelist, etc to facilitate reactive clients tho. Is it lacking or am I not seeing it?<p>Edit: Whey! <a href="http://docs.strongloop.com/display/DOC/Synchronization" rel="nofollow">http:&#x2F;&#x2F;docs.strongloop.com&#x2F;display&#x2F;DOC&#x2F;Synchronization</a>

Can you explain about Mongodb support? Does it use mongoose behind? What about if I have my own mongoose model, can I still continue with same?<p>I did look at loopback a while ago, it was appeared like a parse.com kind of API you host on your own infrastructures. I will reread the documentation again to see if any more clarity on mongodb side.

This framework feels kind of like Rails for REST APIs, but not in a bad way. I really like it so far.

I really like the Angular sdk. I find it really speeds up the process of spinning up a new project

Spent a minute in confusion of the name: LoopBack. Before I have seen another dev tool&#x2F;service with exact same domain but it was about recording the interactions history for your iOS app.<p>Then it occurred to me the iOS rewind service is looKback.io, so close :)

Looks really awesome. Building my REST app with Baucis right now and finding ACL built-in is really nice!<p>Any plans for using Express &gt; 4.x? More and more stuff is targeting Express 4.x these days.

This looks pretty cool! I&#x27;ll be sure to give it a try. It&#x27;s a shame that there&#x27;s no support for Ember though.

Gonna give this a go for my next project, I just hope they implement real-time capabilities like Sails&#x2F;Deployd ASAP

This definitely appears to be the most in-depth and fleshed out Node framework yet. Fantastic docs, too!<p>Awesome work.

Looks great, but what about validation for the models? Didn&#x27;t see that mentioned anywhere.

Love the SOAP connector and storage service. Looking for docs around the offline sync support

Hehe, I owned that domain, loopback.io, a year or two ago. I didn&#x27;t renew it obviously.

This is very impressive.

What&#x27;s the Omega in the terminal??

I thought that LoopBack appeared promising until I came across their astroturf campaigns on reddit. That completely turned me off to them.

hmm, new? no,good for rest rad yes.<p>But we still need a nodejs framework for good old html apps with a strong view layer (e.g. forms...).It definetly doesnt exist in nodejs space.

Didn&#x27;t we all agree that JavaScript is a bad language for development in large? So why won&#x27;t we switch to e.g. TypeScript?