I am a part of a team that uses Meteor in production. We’ve seen that their DDP / reactivity primitives require thought and effort to scale correctly, but they definitely do scale gracefully. And having a UI automatically respond to data changes in mongo can be quite valuable for the right applications.
Like everything in engineering: trade-offs abound. With meteor and the Meteor Guide pattern book, you get a very standardized set of software modules (user authentication, roles, schema enforcement, etc) that cover the entirety of what’s required to maintain a modern, production web application, and all the modules are guaranteed to work well together. But on the flipside: there is far less to choose. It is convention over configuration, to the extreme.
There was a time in my career when I would have appreciated more configuration, but — not entirely sure why — I now get negative joy from that part of the process. For me, Meteor allows me to focus exclusively on the value producing part of the job: the app itself (vs tooling). Fingers crossed that the Tiny team keeps this great system on a path forward!
Meteor. It is quite mature — it is working well for several demanding production applications that our team is maintaining. And I greatly appreciate the breadth and depth of high quality pluggable modules that the meteor team and other developers have assembled. It is very much a “ Convention over configuration“ style platform, going all the way down to their Galaxy hosting service.
Like everything in engineering: trade-offs abound. With meteor and the Meteor Guide pattern book, you get a very standardized set of software modules (user authentication, roles, schema enforcement, etc) that cover the entirety of what’s required to maintain a modern, production web application, and all the modules are guaranteed to work well together. But on the flipside: there is far less to choose. It is convention over configuration, to the extreme.
There was a time in my career when I would have appreciated more configuration, but — not entirely sure why — I now get negative joy from that part of the process. For me, Meteor allows me to focus exclusively on the value producing part of the job: the app itself (vs tooling). Fingers crossed that the Tiny team keeps this great system on a path forward!