Lately, with the help of Julien Tournay, I wondered how can we resolve the model problem in the browser which is : there is no ONE true model, and one information can be duplicated in multiple places (eg: form, list, item). Finally, I found out that the real datas are from : the forms > the server > the DOM. Meteor solved this by keeping this order, and synchronize it all in real time ! That's truly great. But. There a hudge cost in this : you have an heavy fullstack architecture, and you can't have control on the async which is black magic. Also, It's made for realtime, so concurrency apps. With Node.js in one thread, I can't imagine an app with thousands of users at the same time managing as much states properly. There is no holly grail. Just code!
Created
April 11, 2012 21:48
-
-
Save Warry/2362973 to your computer and use it in GitHub Desktop.
My thoughts about meteor.js
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Just run another process using an other CPU for concurrency with a Load Balancer in front as every high traffic websites. Thread is not THE solution.