Architecture Refactoring Along Business Domains Beyond Microservices

Transforming your own software system into microservices? Regardless of this, we software engineers should also better separate existing code along business domains. How do we proceed? Strangler pattern? Not a practical guide.
Conceptually splitting the code into business domains and then refactoring?
Sounds like big-upfront design.
In the talk, we show how to utilise the existing database. How to start from features (in the issue tracker), assign them to domains on a trial basis and evaluate their couplings (overlaps, call dependencies) in the code. Then localise the need for refactoring and evaluate the effort involved. And how automated refactoring proposals play a role in this.

Talk language: English
Level: Newcomer
Target group: Architects, Developers, Product Owner, Quality Assurance, Project Leaders, IT Heads

Company:
Cape of Good Code GmbH

Enes Oguzhan Alatas