Timeline for Server side or client side mvc: which approach imposes less load on the server?
Current License: CC BY-SA 3.0
5 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Oct 14, 2014 at 17:05 | vote | accept | gkaimakas | ||
| Oct 13, 2014 at 16:56 | comment | added | gkaimakas | Sails is great! Currently my team uses ASP MVC for web apps but I find it quite slow (!) and I've been trying to get them to use Sailsjs and Angular and all the awesome tools that exist (Bower, Grunt etc) | |
| Oct 13, 2014 at 16:54 | comment | added | Troy Gizzi | Funny, that's pretty much the same approach I'm thinking of using for my next project: A Node-based REST API (possibly using Sails.js), consumed by an AngularJS front end. I think the future looks very bright for both Node and AngularJS. | |
| Oct 13, 2014 at 16:32 | comment | added | gkaimakas | As far aw team skills as concerned, I was thinking something like a node-based MVC for the backend and AngularJs for the front end. Both being javascript I think that most of the people in my team would welcome the change cause they would be able to maintain both front and back end. | |
| Oct 13, 2014 at 16:27 | history | answered | Troy Gizzi | CC BY-SA 3.0 |