Tight Coupling Made Easy In Microservices

I think with the popularity of microservices, this issue has become a more prominent discussion at code reviews, design meetings etc. There are obvious places like Contracts to be the best abstraction and even distributed in a private package manager feed so that you avoid duplication and don’t repeat yourself.

However, as mentioned in the article, the cost of wrong abstraction in the form of reusing some code piece between microservices is pure evil and strong coupling. It leads to big ball of mud and distributed monoliths.

When they altered their point of view from “I must preserve our investment in this code” to “This code made sense for a while, but perhaps we’ve learned all we can from it,” and gave themselves permission to re-think their abstractions in light of current requirements, everything got easier. Once they inlined the code, the path forward became obvious, and adding new features become faster and easier.

Read on www.sandimetz.com/blog/2016/1/20/the-wrong-abstraction


Published by

What do you think?

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s

This site uses Akismet to reduce spam. Learn how your comment data is processed.