This talk focuses on optimising database queries and using indexes effectively. We’ll look at what to do when queries start slowing down, learn how to analyse query execution plans using the EXPLAIN and EXPLAIN ANALYZE commands, and explore how indexes impact performance.

Through both simple and complex examples, we’ll examine how to improve query efficiency, understand index selectivity, and avoid common mistakes that lead to performance issues.

Everyone knows that tests are important and useful in development. But we also have the infrastructure; what about it? There are also complex deployment scenarios, and the cost of error can be even higher: after all, a wrong configuration of the environment can only be detected during use. 

Let's talk about the value of the IaaC approach and how to test ansible roles with Molecule.

We always hear that Docker makes life easier for developers and QA, but let's figure out how to use it with microservices. 

Let's talk about building and testing all your services with Docker Compose and developing and debugging microservices, stating other microservices in containers.

So, you have become the happy owners of Microservice Architecture. The next challenge is to control quality in the face of rapid code development and low resources. What if we do not have automated End-To-End tests, and there is no way to start a new environment for testing feature branches?

Let's consider Contract Tests as a possible alternative to Integration Testing using the example of Spring Cloud Contract and discuss the pros and cons of this solution.

Microservice Architecture is currently the most popular approach in Web development.  

In this talk, we will discuss why microservices are not a trend for trend's sake but rather a workable tool that solves certain problems better and has many advantages.

We will compare Microservices with Monolithic applications and understand when Microservices should be used and when Monolithic applications should be used.

When we work with a microservice architecture, it often becomes necessary to describe the communication of two services. But how to do it right so that the API looks clear to consumers and is easy to extend and maintain?