Microservices allow for quick development and delivery. But if the code is, let's say, of the legacy persuasion, the development quickly slows down.

Refactoring to rescue.

And this time, it's not just about well-factored, readable code (although we really like it). We'll use common architectural and design patterns that make the code modular, extensible and testable.

In this session, I'll take some (very ugly) microservice API code and refactor it. We'll make sure the domain logic is separated from the infrastructure code, and that the domain logic is unit testable. We'll discuss and use common design patterns (factories, repositories, etc.), and explain how using them helps keep the architecture flexible and maintainable.
Once the code is factored, we'll see what additional tests we can write - and where they help us.

Microservices code should be modular, cohesive and testable.
If it's not - refactoring according to architecture and design patterns is the best way to get there.