Microservices are one of the hot topics of the last years. When dealing with a large legacy application one might not think about them to refactor your current code. But can microservices save you from a world of pain when attempting to rebuild or improve your old application?
This talk will cover the reason why one would or would not use microservices to tackle legacy in large applications, why refactoring often fails without and how to get started. I will talk about how it usually starts to go wrong and how it can go wrong anyway. But foremost i will try to give anyone who has worked on large, higly coupled, legacy applications another approach to refactoring and rebuilding.
12. It can help you to:
● Get a clean start
● Keep your code decoupled
● Make your code testable
● Replace old code with less effort
● Replace or remove old frameworks
● Make bad code less painfull
13.
14.
15. Where to start
● Start small
● Only touch code that you would touch anyway
● The old code is not what you want
16. How to start
● Write dirty code, in a nice way
● Test, Test, Test
● Start at the bottom
17.
18.
19.
20.
21. Pitfalls
● Logging and debugging
● Unnecessary complexity
● Ops
● Team culture
● Company culture
22. Tips
● Micro should not become mega
● Also no nanoservices
● Keep an overview
