What 4 things if not addressed can kill your microservices strategy?

by · Published · Updated

       

Microservices provide freedom from the clutches of the “spaghetti monster” and lets us to the world of flexibility, scalability & agility, but they don’t come free. Here are 4 reasons why!

1. While microservices reduce the “impact” of IT changes through the separation of concerns they can increase the “frequency” of changes that can impact business in the absence of a right level of DevOps maturity, the severity of which rises exponentially as they grow in number.

2. Microservices are founded on the principles of “separation”. This means “isolation” is important in their management from people, process & technology standpoints. Any level of “entanglement” would be a recipe for failure from a philosophy perspective.

3. Transaction management can be big overhead for microservices because a business transaction would be driven by multiple of them running in event-driven patterns with complex rollback & clean-up strategies. Significant automation is imperative.

4. It needs a custom-strategy to establish the basis or a standard in the design or division of services in microservices strategy since every system is different & generalization is not possible.

What is/was your strategy?

Suvo Dutta

I have over 22 years of IT experience in strategy, advisory, innovations, and cloud-based solutions in the Insurance domain. I advise clients in transforming their IT ecosystems to future-ready architectures that can provide exemplary customer experience, improve operating efficiency, enable faster product development and unlock the power of data.

You may also like...