Hi Michael, My app is going to have some heavy computation on the server. I read that this disqualifies Node.JS because it's single-threaded. But maybe I don't know the intricacies enough. The computation isn't going to be implemented in JavaScript, but rather as a separate library that was written in C/C++. I don't have a clear grasp of the connection between Node.JS and outside libraries.
I've been looking closer at angular-app and might not completely understand it. For starters, I have some trouble with just changing something and seeing the effect. It seems like you have to do a whole rebuild and server restart. The other thing is that while they have implemented authorization/authentication in angular-app, it seems to be tied to having the user database at Mongolabs. The application is going to have lots of other data besides user accounts which will naturally be related to user data. So does that mean all the app data should be at Mongolabs? If all the data is at Mongolabs, then shouldn't the application and API also be served by Mongolabs? Can you do this? If you don't do that, isn't that going to create a lot of unnecessary traffic between your app server and Mongolabs? Looking at the Chrome timeline, it seems like getting the data from Mongolabs takes up the most time, by far. Is the intention for people to actually not use MongoDB at Mongolabs but rather install MongoDB on their application server machine? For now, I'm going to look more closely at "generator-cg-angular" and will update the comparison spreadsheet with my findings. Dan On Thursday, May 22, 2014 12:07:35 AM UTC+2, Michael Dausmann wrote: > > Hi Dan > > Thanks for posting that, great comparison. I agree angular-app looks > great. Express/Rails is a big decision, bit like choosing a religion ;) > Express is great because it lets you focus on Javascript on both client and > server, the NPM ecosystem has great depth and high quality and it all just > works. The thing that Ruby/Rails does great IMHO is active record and the > way it handles the database. I haven't seen a comparable equivalent in > Node/NPM yet. Rails also has a great community and is very popular in the > startup scene (although node is growing here too). I personally find that > Node/Express wins because it just works, it is lighter and I can more > easily focus on just the problem I am solving. > > Michael > > On Wednesday, May 21, 2014 11:40:21 PM UTC+10, Dan Cancro wrote: >> >> Hi group, >> >> I made >> this<https://docs.google.com/spreadsheets/d/1r8rJy2Q5p5QORYKcye93UECwOlSgFL24c5fyF7dqhaM/edit?usp=sharing>comparison >> of ten application generators and sample apps that I could use >> to start my own non-trivial AngularJS/RESTful API application. If anyone >> else is doing the same research, this might be helpful to you. >> >> The angular-app generator <https://github.com/angular-app/angular-app>seems >> the best choice for me for the front-end. I'll probably then bring >> in some features from the others. I'm on the fence about using Express or >> Rails for the backend. Does anyone else have a good analysis of the >> trade-offs? >> >> Also, if you see any errors or omissions or mistaken priorities in the >> comparison, feel free to point them out. It's editable too. >> >> Best regards, >> Dan >> >> -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
