126
Monolith vs Microservices (thelemmy.club)
submitted 4 days ago by to c/programmerhumor@lemmy.ml
12 comments fedilink hide all child comments
 

turnoff.us (credits)

you are viewing a single comment's thread
view the rest of the comments
[–] 33 points 4 days ago (4 children)

Maybe an unpopular opinion, but I think if you're not sure if you need microservices, then you don't need microservices. I've had to clean up too many overengineered systems to be convinced otherwise.

  • permalink
  • fedilink
  • source
  • hideshow 4 child comments
    •
  • [–] 22 points 4 days ago (1 child)

    I’ve worked on projects where microservices are a godsend. I’ve also worked on a 12-endpoint REST API atop a SQL database and an Elasticsearch instance serving 500 internal users that somebody had engineered into 8 microservices because management thought microservices were the future. Real mixed bag.

  • permalink
  • fedilink
  • source
  • parent
  • hideshow 1 child comment
    •
  • [–] 8 points 4 days ago

    That's fair. I think they're are definitely systems where micro services are the best choice, but also that they are way over used or implemented too early. Too often it seems service boundaries follow the organization and not the domain model, because they only exist so multiple teams don't have to talk to each other as often. I guess I'm saying there are more incorrect ways of doing micro services than correct ways.

    The worst I've seen though have been a single developer over engineering a system because they thought it was cool, but we replaced it with a simple batch script.

  • permalink
  • fedilink
  • source
  • parent
  • [–] 2 points 4 days ago

    It's going to be a mess regardless. The monolith is just tangled at a different layer. The only way to avoid a tangled mess is to incentivize proper engineering, and everyone is incentivizing time to market and delivery of barely working features, which are the antithesis of proper engineering.

  • permalink
  • fedilink
  • source
  • parent