3 ms·

That's pretty hyperbolic. Are you implying that monolithic designs are just inherently inferior? I don't think that even approaches a reasonable take on the sub

• threeseed 8y ago
  It's a pretty good analogy actually. If you think back to the early Java days when everyone was obsessed with design patterns and over engineered code people said exactly the same thing. Why do you have these interfaces if the implementation will never change ? So I'm not saying monolithic designs are bad but they simply don't scale well once you get to a certain size. Just like design patterns should only be used once your codebase gets to a certain size.
  • EpicEng 8y ago
    I wouldn't say that's quite the same thing, and people _absolutely do_ over engineer/encapsulate their code today. In my own, admittedly limited experience, it seems to me that the biggest win with microservices are realized when you have large teams working independently. There is a complexity overhead that, in my opinion, isn't justified for most apps being worked on by small teams. That said, I don't hold a hard opinion here; I don't have enough experience with them yet. I'm open to having my mind changed.