Transform your own software system into microservices? Regardless of this, we software engineers should also better separate existing code along business domains. How do we tackle this? Strangler pattern? It is not a practical guide on a fine-granular level. Conceptually split the code into business domains and then refactor? Sounds like big-upfront design.

The talk shows how to leverage the existing data pool. How to start from features (in the issue tracker), assign them to domains on a trial basis and evaluate their couplings (design overlaps, call dependencies) in the code. Then use that to locate refactoring needs and evaluate effort. And how automated refactoring suggestions can play an important role in this.

The challenges are the same, we just need to approach them differently.

Problems addressed
* How to separate existing code by domain responsibility?
* How to do the whole thing on a trial basis before refactoring/coding?
* How to use the features of the issue tracker for this?
* How to use the code repository for this purpose?
* How to localize the need for refactoring?
* How do you evaluate the effort for it?