[Ros2]

I made a few Atmosphere packages back in the day, some of them had a good # of users.

Aggregate database queries using Meteor (at least as of 1.0) would create an immense amount of backend overhead if you queried through minimongo. And the overhead was incurred as long as a user was on that page because of how the reactivity worked. I tried making a PR to optimize this but apparently it wasn't comprehensive enough. I kept checking for years but no one attempted to fix this. Before you get nostalgic for Meteor, issues like that were awful.

Meteor (and RethinkDB) were just* pub/sub you had almost no control over. Was fun playing around with, though!

* (also, being able to automatically add accounts and authentication was great)

[winrid]

That's not a Meteor issue. Running aggregations on fact tables at runtime is slow. On top of that, being a document store, mongo is not the best at aggregations. Then instead of using mongo you use minimogo (DB implemented in JS). Then you rerun that query all the time. Of course it'll be slow/expensive. :)