In my opinion, it is a pressing issue. There are at least 2 strategic directions that Meteor could take in the future:
- Improve the original concept of Meteor with mini mongo and DDP making building applications fun and easy. In this case, a monolith approach is probably necessary at least for the back-end.
The point is that Meteor original competitive advantage was simplicity, hiding all the complexity needed to config and deploy a Nodejs/REST project. It was a Ruby on Rails on steroids, less flexible but much more simple and powerful for projects that needed live-update capabilities. Like Rails, Meteor failed to be adopted by the big enterprise for obvious reasons, but it is perfect for small and medium companies and mid-range applications in general—even in the big enterprise.
Now, the Meteor community suffered during the years but its initial adoption was amazing. What we need to know is if Tiny is going to take option #1 or option #2 — maybe there’s a third option, but I can’t figure it out right now.