Complexity is not always good

3 ways projects can be led astray by microservices

Gabriela Motroc

Directional signage image via Shutterstock

Here are a few scenarios in which microservices can add (unnecessary) weight to your project. However, keep in mind that microservices can also simplify development and bolster a cooperative mindset.

More and more organizations are implementing microservices these days, but some seem to have forgotten that there is no such thing as a one-size-fits all when it comes to enforcing this approach. Although it’s extremely important to understand how to approach microservices, it is even more important to know what not to do.

Tareq Abedrabbo, CTO of OpenCredo, explained in a 2014 post titled The seven deadly sins of microservices that the company encountered several anti-patterns (of microservices) on some projects they worked on. As a result, he decided to share with the world all the aspects that didn’t go as expected so that others can mitigate and avoid them.

Not everybody shares the same vision

You may think that everyone has the same vision, but if you fall into this trap, you might invest resources such as time and effort into activities that are unnecessary. If the project’s goals are not clear, it will inevitably lead to “increased complexity and loss of focus in the development effort,” Abedrabbo wrote.

SEE ALSO: “Transition to microservices while running under full steam is not easy”

Ignore the human factor

Microservices can bring simplicity, but that’s not all they bring; developers must understand the bigger picture, as well as the software engineering concepts in relation to how services interact at runtime. Developers who don’t have skills such as fault-tolerance, remote invocation and scalability are likely to fall into countless traps when confronted with a micoservices system. One way to avoid problems is to encourage collaboration across the project (and, if possible, across the company) to design sustainable systems.

Look the other way when it comes to DevOps and testing

The whole purpose of microservices gets lost in too many services as the complexity increases and speed of development and stability drop; failing to understand the importance of DevOps, as well as automated testing practices from the very beginning will have a negative impact on the project in the long run. One of the biggest challenges of microservices is to make sure that the entire system is functional and logical after each alteration.

Microservices offer real benefits such as technology variety and independent deployment, but everything comes at a price. In this case, some of the costs are enhanced complexity, consistency challenges and the list goes on.

Gabriela Motroc
Gabriela Motroc was editor of and JAX Magazine. Before working at Software & Support Media Group, she studied International Communication Management at the Hague University of Applied Sciences.

Inline Feedbacks
View all comments