Changes in database interactions
While we have extracted our application component into its own unit, we continue to be coupled at the database tier. If we are to achieve true independence from the monolith, we need to break this database dependency. Let’s look at the changes involved in making this happen.
Data migration
As a first step to start using a database of our own, we will need to start migrating data from the command side event store and the query store(s), as shown here:
Figure 10.10 – Data migration
In our case, we have the command side event store and the query store(s) that will need to be migrated out. To minimize effort from the outset, it might be prudent to do a simple homogenous migration by keeping the source and target database technologies identical. In advance of the cut-over, among other things, it will be essential to do the following:
- Profile to make sure that latency numbers are within tolerable limits...
