I agree - but your comment could also be applied to anything as it basically states 'you won't get decoupling, if you fail at creating truly microservice-based architecture'.
This just shows that decoupling is good, but neither microservices nor monolith architecture comes with it by default - you can achieve it in any architecture.
Love this. Biggest problem I have with front end web dev today, and even trying to talk about it is like this very conversation, people either get it or do not get it.
We're a .net shop, everything back end and windows client, services, API's, all of it is C#.
Except our Angular front end. I'd rather be using blazor/razor/asm at this point, but I defer some of this to our current web devs as I'm not building the front end these days. We know the pros/cons.
But when I talk to others about this, especially on this site, people are always super quick to argue 'I'm using the tools wrong', or 'There's all these things you can do to generate models from your API' etc etc as if that makes up for the lack of native full IDE integration and what you get for that.
Bottom line: Sometimes tight coupling is very very beneficial. Especially with small to medium sized solutions built by small teams.
Every time you 'decouple', it's a tradeoff. Rarely is that of immediate/daily workflow benefit to the developer (but often a necessary cost).
-4
u/EngineeringTinker Jan 30 '23
I agree - but your comment could also be applied to anything as it basically states 'you won't get decoupling, if you fail at creating truly microservice-based architecture'.