Transition To Micro Services

We have collected the brightest quotes from the discussion about the transition from monolithic architecture to micro services.

How To Sell Micro services To A Business?

We were not selling an approach but a business benefit. There was a problem in business, and we tried to remove it. At that moment, it was expressed that different channels used different principles to calculate the price – separately for promotions, promotions, and so on. It was difficult to maintain; there were errors, and we listened to customer complaints. That is, we sold the elimination of the problem but came because we needed money to create a platform. And they showed a business case using the example of the first investment stage: how we will continue to pay for it and what it will allow us to do.

Our micro services were born from the “foam of the sea” – due to saving resources, some leftovers in the form of server capacities, and the redistribution of forces within the team. Initially, we did not sell this project to the business. It was a project that we both researched and developed accordingly. We started at the beginning of 2018 and set the direction simply on enthusiasm.

How To Evaluate The Success Of The Transition To Micro Services?

First, it was born inside IT as an enabler – “unlocking” new features. We needed to do everything faster for relatively the same money, responding to the challenges of the market. Success is expressed in the number of services reused by different systems and the unification of processes among themselves.Success is more of an inner feeling. Businesses always want more, and the depth of our backlog proves our success.

We have already had more than two hundred services and backlogs for three years. The need for resources within the team is only growing – by 30% annually. This happens because people feel: it’s faster, different, other technologies, all this is developing.

When Are Micro Services Beneficial, And When Are They Not?

Let’s say you have a classic enterprise system. It is located in one vendor’s landscape, consisting of two modules that work with each other. There is also a standard integration interface. Why redo it and bring a micro service there?

But when there are five modules in the back office, from which pieces of information are collected into a business process, which is then used by 8-10 front-line systems, the benefit is immediately noticeable here.

Also Read: How Do You Develop Reliable Microservices?