• 0 Posts
  • 17 Comments
Joined 1 year ago
cake
Cake day: July 20th, 2023

help-circle






  • What’s wild to me is that legal segregation was like, not that long ago at all. It always feels like it’s taught as ancient history but it was only half a lifetime ago, really… and still ongoing. It’s not like this happened a thousand years ago and “you should really be over it by now”, this was the experience of some people’s still living grandparents and parents.

    The idea that an entire demographic of people should magically recover and be equals again after like 30 years of half-assed “equality” after literal generations of slavery is fucking wild.

    Absolute goblin energy to not recognize the ongoing effects of such a recent thing.










  • Tech people tend to be very black-and-white when discussing ideology. Reality is more forgiving.

    If you can get your hands on it, the opening chapters of “Practical Event Driven Microservices Architecture” by Hugo Rocha gives a reasonable high level view of when you might decide to break a domain out of a monolith. I wouldn’t exactly consider it the holy grail of technical reading, but he does a good job explaining the pros and cons of monolith v microservices and a bit of exploration on those middle grounds.


  • The reality is, as always, “it depends”.

    If you’re a smaller team that needs to do shit real fast, a monolith is probably your best bet.

    Do you have hundreds of devs working on the same platform? Maybe intelligently breaking out your domains into distinct services makes sense so your team doesn’t get bogged down.

    And in the middle of the spectrum you have modular domain centric monoliths, monorepo multi-service stuff, etc.

    It’s a game of tradeoffs and what fits best for your situation depends on your needs and challenges. Often going with an imperfect shared technical vision is better than a disjointed but “state of the art” approach.