12 ms·

I agree people hop on the microservice bandwagon without really understanding the "philosophy" behind it. Then blame microservices when they struggle.

• giantg2 6y ago
  I actually prefer a monolith compared to the way we do microservices. One or two big apps to own vs ten microservices or apps that require coordinating with others. It's really just a duplication of paperwork and other overhead processes.
  • UK-Al05 6y ago
    We don't require any coordination with ours. It's low cost for us. We may make the occasional announcement that v5 our api is coming soon which has x features based on feedback from other teams. Then announce when we've released it. Its a product, and we own it.
    • giantg2 6y ago
      That sounds nice. My most recent elevation involved coordinating with 5 other services to stop/restart/reprocess items with a couple deploys between the 5. Had to be off-hours too. Sort of normal for us.
      • UK-Al05 6y ago
        You have all the symptoms of a distributed monolith.
  • ex_amazon_sde 6y ago
    > vs ten microservices or apps that require coordinating with others That's called the "distributed monolith" and it's worse than a monolith.