Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

LoopBack, a new Node.js framework by StrongLoop

loopback.io

Post reply on HN
Print view View original

41–50 of 67 posts

Re: LoopBack, a new Node.js framework by StrongLoop

#42

Post by segphault »

For node-based API backends, I'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't look like LoopBack does that.

I'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.

Re: LoopBack, a new Node.js framework by StrongLoop

#44

Post by angersock »

rmgraham wrote: post #35
hardwaresofton wrote: post #31

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/backend 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…

Postgres almost warrants its own non-generic ORM. That would actually be kinda cool.

Hmm....

Especially exposing some of the things like intervals, the geographic features, and a lot of their other cool things.

Yeah, I could live with that.

Re: LoopBack, a new Node.js framework by StrongLoop

#45

Post by angersock »

segphault wrote: post #42

For node-based API backends, I'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't look like LoopBack does that. I've been particularly happy with Sails.js as the backend framework for my single-page web a…

I've been considering using Sails to redo a simple RoR project--mostly to help decrease the number of languages floating around in the project.

Any thoughts/gotchas from your experience with it?

Re: LoopBack, a new Node.js framework by StrongLoop

#47

Post by hardwaresofton »

rmgraham wrote: post #35
hardwaresofton wrote: post #31

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/backend 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…

Postgres almost warrants its own non-generic ORM. That would actually be kinda cool.

If I understand your comment right, are you looking for something like this:

http://bookshelfjs.org/

I haven't done much work with a relational DB from nodejs (I've just used nosql databases that offered relational functionality -- i.e. rethinkdb), but this seems like as good a thing as any for ORM-y stuff with Postgres

Re: LoopBack, a new Node.js framework by StrongLoop

#48

Post by hardwaresofton »

enjoyjava wrote: post #37
hardwaresofton wrote: post #31

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/backend 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…

Good catch. We support Postgresql, MS SQL Server, and SOAP too.

Great!

I'm actually considering using this in a new project right now - it is very very tempting to think that I could just use this, and have a middle-layer that I don't have to muck with... this would greatly speed up development, I do applaud the team for trying something so ambitious, could be huge

Post reply on HN