In our current microservice, we store the data that doesn't belong to us and we persist them all through external events. And we use these duplicate data (that doesn't belong to us) in our actual calculation but I've been thinking what if we replace this duplicate data with async webclient on-demand calls with resilience fallbacks? Everywhere we need the data, we'll call the owner team through APIs. With this way, we'll set us free from maintaining the duplicate data because many times inconsistency happens when the owner team stop publishing the data because of an internal error. In terms of CAP, consistency is more important for us. We can give the responsibility of availability to the data owner team. For why not monolith counter argument, in many companies, there are teams for each service and it's not up to you to design monolith. My question, in this relation, is more about the general company-wide problem. When your service, inevitably, depends on another team's service, is it better to duplicate a data or async on-demand dependency?
↧