Too Long; Didn't Read
There are several ways to handle data in a microservice architecture, in this article we will cover the approach of having a separate database for each microservice. This article will build upon the concepts covered in the following video by [Houssem Dellai]. The following diagram shows the architecture as described in the video above: The materialized view will be used as a read-only data source for the Basket service. The downsides of this approach are: There will be a duplicate of the data in the aggregator. The change events would add lots of complexity to the microservices.