We are using Meteor and have been for about a year. The biggest caveats are : 1) MongoDb - I know the NOSQL really believe that NOSQL is awesome... but it isn'

We are using Meteor and have been for about a year. The biggest caveats are : 1) MongoDb - I know the NOSQL really believe that NOSQL is awesome... but it isn't. SQL support is coming - but isn't there yet. 2) NodeJs on the server - Once again the single thread model has its true believers. My response: preemptive scheduling and multithreaded environments were created for many good reasons by people smarter than I (or you). Sure it is possible that you may do o.k. with it. Just remember 1 bad call kills the entire server. 3) It is still maturing and changing. 4) Suggested coding style is a little sloppy with security 5) Performance issues are still being addressed. (pub/sub model imposes burden on database) Positives: 1) It is cool to write code that runs on both client and server 2) The pub/sub module to ship data to the client and keep it refreshed is a definite win. 3) packaging system is pretty good. 4) Meteor leverages the nodejs community. ( it is pretty easy to shim a npm package into meteor ) More later if desired.