3 ms·

> Monoliths require alignment. So do microservices.

• spicybright 3y ago
  I think GP's point on company culture is the right answer. My only thoughts to add is monoliths can be aligned as well as microservices, if not a bit easier depending on the team. You have to align microservices to talk to each other anyways, and there's no reason you can't make those boundaries work in one codebase instead of many. That said ownership is more important in a monolith, whether that be a single team of architects or architects responsible for a specific well defined part of the code base. Having a solid process for only allowing well thought out code in is a cornerstone to keeping alignment.
  • zerbinxx 3y ago
    The worst thing is the many-monoliths/mini-monoliths problem that you get when each team thinks it has ultra special needs and absolutely must build everything from scratch, even if it’s a near duplicate of something someone else built 2 months ago.
    • ilyt 3y ago
      building from scratch instead of using something that already fits pretty well is orthogonal to discussion as it happens both in monolith and microservices
• deleted 3y ago
  [deleted]