I want to discuss converting from bold DB to microservice architecture.
A bit of history:
Thus, we have a system of long-term loans that records customer details in the FAT database with more than 1000 tables. The application does much more than just a loan capture with more than 100 screens / processes built outside of a loan capture. Like administration, reporting, configuration, etc.
Current status:
The entire presentation level, logic level, database level, ORM level are part of one project.
The current task in hand: The
application is built in Win Forms, and my work turns it into a modern user interface, because we need a modern function.
Approach:
The approach that I take is to create some microservices on the current database structure. Using the same database will allow the current application to start as is, and we can write a new database level, a logical level in some microservices. Then we can write a Modern User Interface (angular / response) that will use these services. Then in the second stage, the use of the capture operation from the old application will stop.
The third step is to move specific database tables from legacy databases to your own databases.
This approach seems to be the best if you support the current work as is. In addition, this approach allows us to run both applications in parallel in a production environment.
Confusion: The
question I have is the detailed design. I'm struggling to understand the context divided into Micro Services. Information in the field of the first iteration: - Some qualification questions - Contact information - Requirements for applications - Information about the bank - Information about income - Details of expenses - Previous information about the loan
Microservices that I believe have - Application service - Qualified issues - Application requirements - Previous loan information - Income / expense information - Demographic information - Bank information - Contact information
:
- ?
- . - , ?
.