Goodbye routine: how to organize microservices development

At the Java Meeting Point conference, Andrey Perepelkin from the Square Meter real estate ecosystem will tell you how to organize the development of microservices in order to make them as similar as possible and remove routine tasks from developers.

Andrey has a lot of experience in this business: he and his team organized a process in a company where today there are 50 microservices, and this number is constantly growing. In this interview, he talked about the challenges he faced and shared his success in solving them.

What will you tell the conference participants about?

I will tell you how we managed to organize the development of microservices in order to remove from the developers all the routine of integrating them into the infrastructure. We also paid great attention to ensuring that engineers were quickly informed of any changes at the company level.

With what knowledge is it worth coming to the report?

It’s great if you have experience in developing microservices. I will talk about the current stack: Spring, Spring Boot, Spring Cloud, Kubernetes, Helm, a basic understanding of them will come in handy.

What were your tasks? What have you achieved?

Our company’s projects are a large ecosystem, within which there are many related products. Today there are about 50 microservices, and their number is likely to grow. The development was carried out for several products at the same time, and our task was to ensure that the teams were in a single IT landscape.

Now, to create a microservice and fit it into the landscape, put it on monitoring, get logs, connect it to the deployment system, it takes a little time. For example, creation and deployment takes an hour or two.

At the same time, despite the fact that the process is not described, engineers do not have any questions – everything is intuitively clear, even if a person, say, is recently on a project and does not know all the details. I saw how, in the same banking sector, it happens that you need to read several instructions in order for the microservice to fly into the infrastructure. Everything is easier and faster with us.

Conference participants will be able to take advantage of our approach or part of it. It can also be transferred to projects of a different scale. It will turn out to learn how to make friends with each other tools.

Java Meeting Point will take place on June 23rd, join us! More about the program – here

Similar Posts

Leave a Reply