Meteor in Production
blog.geekli.st
Meteor in Production
1–10 of 34 posts
Re: Meteor in Production
#2If you need to strip a lot of boilerplate and modify the code of a large framework in order for you to use it enjoyably, maybe you should look into different frameworks instead? Perhaps a microframework.
Re: Meteor in Production
#3I didn't use demeteorizer for https://lawyermatch.me, but after making a meteor bundle you just get a node app anyway, so deploying to production didn't really hold any surprised in store for me.
Related to production-meteor, I guess phusion passenger supports meteor now, does anyone have experience with the pluses or minuses of passenger over node/forever + nginx? LawyerMatch has been a way for me to test new tech to begin with, so I'm interested in giving passenger a try for a production app...
Re: Meteor in Production
#4If you need to strip a lot of boilerplate and modify the code of a large framework in order for you to use it enjoyably, maybe you should look into different frameworks instead? Perhaps a microframework.
I think you misunderstood the article. There is no stripping of any boilerplate, but rather converting the existing project to how meteor runs itself as a native node.js application, in order to run it in production. That way, you can use a number of other tools to keep it running (forever), to load balance it with other instances (http-proxy) or monitor it (newrelic).
Re: Meteor in Production
#5I ran a meteor app as an entry system for a local design awards show last month. Everything went swimmingly well and people loved the fast app-like interface. The only place I had trouble was on the admin side where large amounts of items were sometimes not loading properly (usually a page refresh would clear the problem though). My takeaway was 1) This is beta software people, of course its not going to be perfect and 2) Deciding what should be sent to the client takes some thought and I could have almost certainly made things more efficient. With time, I think both of those issues will be resolved what with the highly active meteor community and MDG making great progress on the framework, and with me thinking more 'meteor-like' and building my apps more efficiently.
Re: Meteor in Production
#6I ran a meteor app as an entry system for a local design awards show last month. Everything went swimmingly well and people loved the fast app-like interface. The only place I had trouble was on the admin side where large amounts of items were sometimes not loading properly (usually a page refresh would clear the problem though). My takeaway was 1) This is beta software people, of course its not going to be perfect a…
did you make sure that you don't have the insecure package installed, that pushes the entire database to each client, and instead are subscribing to the data? this is reminiscent of how one one of proof of concept apps was acting a few months back and that was the cause.
Re: Meteor in Production
#7Author asserts Meteor scales poorly, which inspired his script "demeteorizer" which helps only if the project is deployed to author's hosting service "modulus.io"
Re: Meteor in Production
#8Author asserts Meteor scales poorly, which inspired his script "demeteorizer" which helps only if the project is deployed to author's hosting service "modulus.io"
I think the author was only talking about how to make Meteor scale on any hosting service by making it into a raw node.js app, something that more people have experience scaling. The NPM package demeteorizer, which was written by the modulus team, can actually be used to turn any meteor app to a core node.js package, which can then be hosted as you would any other node.js apps and can use any node.js hosting service (nodejitsu, heroku, appfog, modulus.io) or roll your own on bare metal (dedicated/aws).
Re: Meteor in Production
#9I ran a meteor app as an entry system for a local design awards show last month. Everything went swimmingly well and people loved the fast app-like interface. The only place I had trouble was on the admin side where large amounts of items were sometimes not loading properly (usually a page refresh would clear the problem though). My takeaway was 1) This is beta software people, of course its not going to be perfect a…
did you make sure that you don't have the insecure package installed, that pushes the entire database to each client, and instead are subscribing to the data? this is reminiscent of how one one of proof of concept apps was acting a few months back and that was the cause.
Sure, thats Meteor 101 ;) Still, as a developer you need to decide what collections you want to publish (and which parts of each collection) so as to make the application run blazing-fast but also make sure you're only publishing stuff when its needed. This, IMO takes some finessing to get right.
Re: Meteor in Production
#10Earlier quoted context omitted.
did you make sure that you don't have the insecure package installed, that pushes the entire database to each client, and instead are subscribing to the data? this is reminiscent of how one one of proof of concept apps was acting a few months back and that was the cause.
Sure, thats Meteor 101 ;) Still, as a developer you need to decide what collections you want to publish (and which parts of each collection) so as to make the application run blazing-fast but also make sure you're only publishing stuff when its needed. This, IMO takes some finessing to get right.
ah ok :) interesting, could you share some of the code in question, or is this a closed source app? I'd be happy to take a quick look