The document discusses transitioning from legacy code to a microservices architecture, highlighting the potential benefits such as achieving a clean start, decoupling code, and making it more testable. It outlines practical steps to begin this transition, such as starting small and focusing on existing code, while also identifying common pitfalls and offering tips for success. Ultimately, it emphasizes that microservices won't fix all problems, like poor coding practices or slow applications.

1. Taking out the legacy
the microservice approach
Niels van Esch
@goatcode
https://joind.in/talk/41aff

2. Fighting the legacy
● Based on a true story
● What will it fix?
● Where and how to start
● Common pitfalls
● Tips

3. Perfect world

4. Reality

5. Microservices

6. Microservices

7. Why my code sucks
● Deadlines
● Temp hacks
● POCs
● Frustration
● I am human
● I learn

8. What will it fix?

9. What won’t it fix?
● Bad coding
● Slow applications
● Bugs
● Monolithic classes
● Anything else

10. What will it fix?
● Nothing

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

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

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

27. Niels van Esch
info@nvanesch.nl
@goatcode
https://joind.in/talk/41aff