How does meteor compare to a service based architecture?


#1

As my understanding, with a service based architecture you just split everything into separate services and each service is fairly easy to scale by just duplicating the service instance.

With Meteor it seems everything just runs in one big queue one by one, whereas with a service based architecture I’m guessing you just direct to different service instances, making it more efficient to scale. With meteor I guess you’d have to run more meteor instances, however each meteor instance may run several “services”/tasks at once, meaning it should be harder to scale?

Can you give me a bit of an overview of how Meteor compares to a service based architecture on scale?