State of Meteor?



Actually is not that hard to use both.

You can check this docs and package to use with ostrio:files,

And if you need to see an example, check my public repo Urbanus.

Make sure you check both Team and Image Api’s.

If you need anything just ask! Good work.


Thanks Fillipe, seems like this is just what I needed as an example!
This is another amazing thing about meteor: the community is awesome too.


EducationLink has been running smoothly for 3 years now. We use Vue.js. (
We have three different Meteor apps for three different types of users, all connecting to the same MongoDB Atlas instance. For background functions we use AWS Lambda. We also have some special APIs on API Gateway.


Since it is also related to this post, I would like to encourage everyone to participate in the community survey.


Have to say that it’s making a point.


I’d been a long-time ColdFusion developer (yikes! since 1996) and loved how quickly you could develop multi-featured apps with not a lot of code. I switched to Meteor around 3 years ago and have 7 Meteor apps built of various complexity and features. Like ColdFusion, it’s easy to build things “incorrectly” that can impact the performance or reliability of the application. i.e. both platforms give you enough rope for you to completely strangle yourself with.

The hardest part is optimizing Meteor’s pub-sub and memory consumption. One thing that doesn’t get mentioned much is the performance of the underlying database provider. After switching some of my apps to fast-network, SSD-based MongoDB instances, I could see much faster performance in several parts of my apps.

As previously mentioned, I do sometimes rely on methods to retrieve data, since the awesome reactivity pub/sub provides isn’t always necessary, or worth the penalty.

I’m currently working with Vue, Vuetify and Vuex for the front-end (no Blaze at all), and must admit it’s been tougher than expected to get started because there seems to be MANY ways Vue can be integrated with Meteor without really seeing a “Best Practice” obvious path. The online examples are all over the place, but the single file components truly are sweet!

I have no short-term plans to switch away from Meteor, but there’s also the thing about using the right tool for the right job, and I can see where Meteor might not be the best fit in all cases.


I’m developing software in meteor since 4+ year. Solo and in teams. Clients in public and private sector. And I’m very happy with meteor and will continue using it in future projects!


nodeJs (zeit now)
[ more characters.]