This is the story of how we need to change an existing monolithic system to be able to run over microservices. Lessons learned and best practices will be presented together with the most important architecture patterns that we need to take into account when we need to do such a migration. Migration is not a simple task, this is why it is important to learn from our past experience.

5. Maintenance
is hard
Adding new
features is slow
Changes are
expensive
Technology
becomes the
obstacle
rather than
enabler

6. RADU VUNVULEA MCTS MCP BANK HOME AUTOMATION
MVP ENTERPRISE
AUTOMOTIVE PHARMA
LEAN AND AGILE E-COMMERCE
WEB iQuest
AZURE JAVASCRIPT VUNVULEARADU.BLOGSPOT.COM
MOBILE DOTNET @RaduVunvulea
WCF WPF ENTHUSIASTIC

9. Gradually migrate
Run in parallel
Add new features as
microservices
Migrate modules

18. • the monolith will disappear
OR
• it will become small enough that is just another
service

21. Define a coarse-grained interface
• Challenge when Domain Module Pattern was used because of the associations
Turn the module in a free-standing service
Hook the service into the system through the interfaces
Integrate with microservice solution

24. Service
Granularity
Share
Code
between
Services
Doing to
much or
to little

26. Question
Answers

27. {
“name” : “Radu Vunvulea,
“blog” : “vunvulearadu.blogspot.com”,
“email” : ”vunvulear@outlook.com”,
“socialMedia” :
{
“twitter” : “@RaduVunvulea”,
“fb” : “radu.vunvulea”
}
}

28. Today: Take a look on Uncle Bob’s article about microservices
Tomorrow: Start the migration 

29. {
“name” : “Radu Vunvulea,
“blog” : “vunvulearadu.blogspot.com”,
“email” : ”vunvulear@outlook.com”,
“socialMedia” :
{
“twitter” : “@RaduVunvulea”,
“fb” : “radu.vunvulea”
}
}