Skip to main content

You are not logged in. Your edit will be placed in a queue until it is peer reviewed.

We welcome edits that make the post easier to understand and more valuable for readers. Because community members review edits, please try to make the post substantially better than how you found it, for example, by fixing grammar or adding additional resources and hyperlinks.

Required fields*

4
  • 1
    “and in such cases a microservice can be easier to develop” – did you mean to talk about monoliths there? Commented Apr 23, 2018 at 12:14
  • @amon Thank you, I have corrected the sentence - my son did interrupt me 34235 times so I was confused ;) Commented Apr 23, 2018 at 12:40
  • While I agree with your first sentence, I think you should consider that even your monolith should already be "modular-like" inside, otherwise you just won't be able to separate anything without having everything falling. Commented Apr 23, 2018 at 13:32
  • @Walfrat I tend to agree, but the temptation to reuse existing code is much greater (and less easily squashed) in a monolith. E.g. "oh look, somebody defined an WidgetId, I will just reuse that for my FormId": Also, you cannot easily use another language / db for a project, which really fosters the "everybody must use common tools" thinking Commented Apr 23, 2018 at 13:57