Meteor for static read-heavy apps?

1

I love using meteor because of its command-line tools, no need to setup anything, just add packages and you’re good to go.

However my app is mostly static, to save memory and making it more scalable I am thinking about using Meteor methods to retrieve data instead of subscribing to them.

It is just as easy as subscribing to datas, same code with meteor.methods instead of meteor.publish, and meteor.call instead of meteor.subscribe.

My question is , is there ANY big down side for doing this? how does this compare to something like an express.js or rails back end?

1 Like
2

Yeah the biggest downside here is that you no longer get caching from Minimongo - Meteor automatically deduplicates data sent from subscriptions.

However, there isn’t any downside to doing this compared to Express or similar, because it doesn’t have those features anyway.

3

I agree with sashko. With server side rendering, we can do pretty good job for these kind of apps.

4

I’m also interested in building sites where reactivity is minimal. Here are some related resources in case you haven’t collected them already:

https://github.com/meteorhacks/subs-manager - in some cases this may be all you need

https://github.com/ccorcos/meteor-subs-cache - variation on the above

https://github.com/richsilv/meteor-dumb-collections - uses methods under the hood

https://medium.com/@msavin/scaling-down-subscriptions-and-reactivity-in-meteor-57bf3c0652ca - describes a method approach using Fetcher

2 Likes