3 ms·

You don't need to run queries, you subscribe to queries. As the data updates your app will be able to react to it without having to run a query. For really "big

You don't need to run queries, you subscribe to queries. As the data updates your app will be able to react to it without having to run a query. For really "big data" you are probably going to want to supplement your application's architecture with something specifically designed to work with "big data" just as you would have to with any web framework. The new smart package feature in meteor.js was intended for adding new things like this into your app.

bjourne 14y ago
The difference is academic. There still has to be a database that runs queries even if Meteor prefer to think of it as a subscription. The reason I used "big data" in quotes is because 100k rows isn't really that big. Most other web frameworks has no problem dealing with it, but with Meteor it's almost impossible.