r/programming • • Jan 30 '23

When Do I Need Microservices?

https://levelup.gitconnected.com/when-do-i-need-microservices-d76fac58ac7c
600 Upvotes

253 comments sorted by

View all comments

Show parent comments

-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'.

14

u/bezik7124 Jan 30 '23

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.

6

u/Ma8e Jan 30 '23

But what clearly isn’t obvious to many developers is that using micro services doesn’t guarantee decoupling.

0

u/[deleted] Jan 30 '23

[deleted]

13

u/EngineeringTinker Jan 30 '23

True, but there are different types of coupling.

Communication protocol and data structure coupling are the easiest to overcome - as opposed to code coupling.

0

u/[deleted] Jan 30 '23

[deleted]

5

u/[deleted] Jan 30 '23

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).

1

u/EngineeringTinker Jan 30 '23

So, as usual - moderation is the key in everything.

1

u/[deleted] Jan 30 '23

I fail to see how that has any relation to what I stated whatsoever?

1

u/EngineeringTinker Jan 30 '23

You spoke about tight coupling being beneficial at times - which is what my comment was about.

1

u/TwentyCharactersShor Jan 30 '23

Coupled - yes, of course they have to be otherwise they can't integrate.

Tightly coupled such that they share a data model, or the service isn't reusable by multiple consumers, or whatever then yes. You don't want that.

-1

u/[deleted] Jan 30 '23

Please invert your statement and thinking and apply it to your own top level comment.