The first step in the process is to create a shared module. Given the archtecture, APIs are separated into separate projects according to domain area. We are taking a microservice type approach in such that instead of a single monolith application, we are destructuring the code based into multiple modules. This does create a requirement to share code across the modules.
Modern day package managers support the ability to define local dependencies in addition to remote shared community libraries.
I can make an educated guess about which code should live in the shared module, however the initial draft, I tend to define code in the appropriate model, only migrating the code into the shared module once at least a single other requires the same code.
Determining which code lives in the shared module can be difficult to determine at times, however the following are what would be called common dependencies across all applications.
Given the fact that this is a greenfield effort, there wwill be a lot of boilerplate code involved in the initial efforts. In order to streamline efforts, code generation will be utilized whenever possible.
Addiional middleware was implemented to strealine the process of working with pagination parameters.