More talks in the program:
When migrating an existing application to a microservices architecture, a key consideration is how (or whether) to reuse the current/working code. There may be a substantial cost implication to making a good decision on this. Ultimately it boils down to how feasible it is to partition the monolith into smaller chunks of functionality that can be ported to the microservices framework.
When the existing application is already organized into modules, these can make good candidates for microservices. However more often than not, one or more modules will have become monolithic and must be further decomposed if the benefits of microservices are to be realized.
How we go about this depends on the dependency structure of the code in the monolith, and how features that we may like to extract are distributed across this dependency structure.
This talk will show by examples how different strategies can be employed to decompose monoliths with different dependency characteristics.