News for hackers. Stuff that matters.
Re:Ten Years and Counting: My Affair with Microservices by bobthepanda on Saturday April 13, 2024 @10:19PM (#40028147)
the theoretically nice thing about microservices is that because the API boundary should be well defined, any possible application that can fulfill that API, whether it's Java, Rust, or three raccoons in a trench coat can become the new microservice fairly easy.
Re:Ten Years and Counting: My Affair with Microservices by exe34 on Sunday April 14, 2024 @05:02AM (#40029781)
All we have are three raccoons in a trashcan, but you'll be able to fit this in the current sprint, right?
Re:Ten Years and Counting: My Affair with Microservices by john_the_writer on Sunday April 14, 2024 @06:30AM (#40030139)
The problem with that. Maintenance. Team X writes a micorservice in Node. Team A->W write in elixir. Bug in Micro_X and tada... company is screwed. No one wants to learn Node, so the bugs stay around, get worked around and then Micro_X gets re-written in elixir, because coders have to fix stuff.
Re:Ten Years and Counting: My Affair with Microservices by thesnide on Sunday April 14, 2024 @07:18AM (#40030334)
That is painfully accurate. My usual response to it is https://despair.com/products/break-the-rules

It usually gives me angry looks at first, but thanks after several years when there's enough turnover.

Re:Ten Years and Counting: My Affair with Microservices by bobthepanda on Sunday April 14, 2024 @03:23PM (#40033635)
Terrible engineering is also possible in the monolith, it’s just significantly harder to rewrite sour bits of monolith independently.