3 ms·
"2) relegated cpu-bound work to micro-services that could process work from a queue at their own pace" doesn't this defeat the primary selling point of meteor?
by qaq 10y ago
"2) relegated cpu-bound work to micro-services that could process work from a queue at their own pace"
doesn't this defeat the primary selling point of meteor?
- ben_jones 10y agoThe three key features we derive from Meteor are: 1) real-time view layer 2) diverse and highly integrated ecosystem (libs are written just for meteor) 3) productive development environment (es2015 modules on client/server, no fuss build pipline for sass, jade, angular-templates, angular dependency injection) There are a ton of secondary benefits, but thats the crux of it. Yes we do sacrifice some of the benefits of Meteor as a monolithic (homogenous?) full-stack solution, but I would argue that they are in fact small, and if you dive into Meteor you'll find it to be pretty modular.