Refactoring a monolith to Microservices


Details
Microservices are all the hype off late. They promise separation of business functions into units that can be developed, deployed and managed independently of other services, and are maintained by a single team.
All of that sounds nice, but how do you get there? How do you go about transforming a dinosaur into a herd of gazelles?
We have been carving up a digital dinosaur to see what challenges we run into, like choosing service boundaries, communication between services, and refactoring code.
To participate you’ll need a laptop with Java and Maven installed. IntelliJ will probably make your life easier. We’ll be using Spring Boot and provide a repository on GitHub.
Program
18.00 Dinner
18.45 Welcome
18.50 Theory: steps to take when refactoring to Microservices
19:30: Exercise: Identifying services and boundaries
20:00: Exercise: Improve robustness by implementing circuit breakers
20:30: Exercise: Loose coupling in time, from REST to messaging
21.00: Wrap up

Refactoring a monolith to Microservices