Undoubtedly, the adoption of microservices has made it possible for companies with dozens or hundreds of teams to put software into production in an isolated and independent way at different paces without one team stepping on the other's toes. However, we can not ignore that despite the organizational advantages brought by this architectural style, we had to embrace its inherent complexity that, in essence, left the code and ended up at the edges.

Even small business logics are no longer local calls in memory within the same process and are now remote calls between services in an inherently unstable network. Ensuring that these logics work as expected is a challenging task, and relying solely on unit tests can be dangerous and a one-time mistake.

In this talk, I will discuss why unit tests alone are inadequate to guarantee the correctness of your code, reveal bugs earlier, or even allow the evolution of your application in a safe and sustainable way. Not surprisingly, we will understand why favoring the writing of integration tests and embracing the facilities of your IoC/DI framework can be crucial for developing, maintaining, and delivering your microservices.

If you trust that your unit tests are sufficient, this talk is for you, dear developer.