3 ms·

TBH, his definition of "module" brings it awfully close to microservice.

• JAlexoid 4y ago
  Common definition of a microservice is basically a module. This is not the first thread on the topic. And considering the number of people actively defending microservices, like it's debates about iPhone vs Android over a decade ago - I'm going to say that too many people can't rationally look at this at this point. Too many emotions flying around.
• gfodor 4y ago
  I thought he was referring to typical in-process encapsulation. If you do that well, you can run those separately “for free” optionally, but I think his definition of module is nothing unique.
  • _ea1k 4y ago
    From the article: "Modules which can be easily be deployed independently - when the need arises." I read this to mean that they would always be deployed independently, but now I think I misread it. He actually meant that they should be really easy to split. In practice, I think people with this view underestimate the difficulty in splitting even seemingly unrelated services from a monolith. Its never completely trivial. Its better not to start that way if it is foreseeable as an undesirable end state.