This looks amazing, and the StrongLoop team is chalked full of some great Node.js developers. But for some reason I'm still worried about using it as the backbone for an enterprise scale application; it almost does too much. Perhaps I'm just too averse to this amount of "magic" in any piece of infrastructure due to my Django days. The code is open, but you're not just buying into a single module with a single purpose…
LoopBack, a new Node.js framework by StrongLoop
61–67 of 67 posts
Re: LoopBack, a new Node.js framework by StrongLoop
#62For 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…
Re: LoopBack, a new Node.js framework by StrongLoop
#63Re: LoopBack, a new Node.js framework by StrongLoop
#64Looks really awesome. Building my REST app with Baucis right now and finding ACL built-in is really nice! Any plans for using Express > 4.x? More and more stuff is targeting Express 4.x these days.
Putting that conversation aside, I'd be very interested to know what advantages there are for you in having ACL built-in vs. using one of the ACL middleware modules that are available through npm.
William Riley-Land (Author of baucis)
Re: LoopBack, a new Node.js framework by StrongLoop
#65Wow, I'm building something a bit similar in the Go area: https://github.com/sergiotapia/paprika Nice to know it's a good idea that a lot of people will find useful. :) Granted in it's current vision Paprika won't handle authentication. It's basically an API server in-a-can. Defined your structs, set up your .toml database configuration and paprika.Start("3000") on a port.
I've seen ton of "expose DB as REST-like API" libraries in various languages, and even tried (unsuccessfully) to write one myself. I'd say just exposing model is trivial, even when coupled with content-type negotiation. Subjectively, the hardest part is permissions (operation, row and field-level ones) and making them play nice with REST and HTTP concepts (like ETags).
What interests me a lot at the moment are HTTP proxies that provide features like these. I like the encapsulation and scalability that true REST makes easy.
I would say writing the "expose DB as REST-API" can be easy for small projects, but a lot of work can go into making something that is RESTful, scalable, and a joy to build with.
Re: LoopBack, a new Node.js framework by StrongLoop
#66Looks really awesome. Building my REST app with Baucis right now and finding ACL built-in is really nice! Any plans for using Express > 4.x? More and more stuff is targeting Express 4.x these days.
Baucis takes the approach that monolithic frameworks are more costly in time and resources to build software with in all but the short term, and only then sometimes. Long live small libraries! Putting that conversation aside, I'd be very interested to know what advantages there are for you in having ACL built-in vs. using one of the ACL middleware modules that are available through npm. William Riley-Land (Author of…
That been said, there are a lot of node.js modules out there and I could simply miss right one. If you could point to a couple you think might play very well with baucis - I would really love it.
In general most of rest/mvc frameworks our there miss this part entirely. I am ok with acl being not part of particular framework as long as there is at least one 'blessed' combination to use.
= pavel karoukin - author of baucis-access plugin :)
Re: LoopBack, a new Node.js framework by StrongLoop
#67Earlier quoted context omitted.
Baucis takes the approach that monolithic frameworks are more costly in time and resources to build software with in all but the short term, and only then sometimes. Long live small libraries! Putting that conversation aside, I'd be very interested to know what advantages there are for you in having ACL built-in vs. using one of the ACL middleware modules that are available through npm. William Riley-Land (Author of…
Requirements for ACL for json fetching/saving and regular rest endpoints are a bit different, so I couldn't find exact fit so far. In most cases you have to define a function, which become too verbose with very little re-usability. That been said, there are a lot of node.js modules out there and I could simply miss right one. If you could point to a couple you think might play very well with baucis - I would really l…
What're your "killer features" that are lacking for ACL in Node in your experience?
I'm becoming severely intrigued by the idea of using specialized proxy servers for applications like this…