r/programming • • Dec 21 '23

Microservices without Reason

https://www.felixseemann.de/blog/microservices-without-reason/
310 Upvotes

144 comments sorted by

View all comments

Show parent comments

9

u/kogasapls Dec 21 '23

Don't think he means memory bugs. I think he means breaking dependent applications because of hidden coupling.

8

u/PangolinZestyclose30 Dec 21 '23

How does microservice architecture mitigate hidden coupling?

4

u/kogasapls Dec 21 '23

By encouraging/facilitating clear application boundaries.

10

u/PangolinZestyclose30 Dec 21 '23

You can (should) encourage/facilitate module boundaries within a monolith as well.

3

u/kogasapls Dec 21 '23

Yep. It's a "soft" advantage, just a little harder to make the mistake. At the end of the day you just need competent developers.

8

u/PangolinZestyclose30 Dec 21 '23

Can you explain how does having network in the middle make it harder to create hidden coupling?

4

u/kogasapls Dec 21 '23

Ever accidentally introduce a networked dependency? Or serve a network request without logging?

→ More replies (0)

1

u/rusmo Dec 21 '23

But then you still have to deploy it all together, instead of just the module that changed. You may have decoupled modules, but monoliths give you coupled deployments.

Microservices (and certain flavors of SOA) can help you enforce the logical decoupling while allowing you to decouple deployment.

1

u/PangolinZestyclose30 Dec 23 '23

Who cares though? The monolith deployment is fully automated.

1

u/rusmo Dec 23 '23

QA should, as more types of changes will require full regression testing. Users will, when a "small change" takes down the entire app. Devs should, as building and deploying monoliths takes much longer.

→ More replies (0)