Conflicting advice on Materialized View pattern

Hi,

In this page you state...

> Another solution for aggregating data from multiple microservices is the Materialized View pattern.

...with a link to https://docs.microsoft.com/en-us/azure/architecture/patterns/materialized-view.

On the linked Materialized View pattern page it states:
> This pattern isn't useful in the following situations:
>...When using microservices

This is contradictory and confusing, which doesn't help increase our architectural knowledge.

It would be really good to understand the most common and most well-regarded approaches to the problem of "Challenge #2: How to create queries that retrieve data from several microservices". For instance, other documentation on this challenge mentions the use of events to capture data and create a local cache of the required data from other services. Is this a good pattern? What are the pros and cons of these patterns, in what scenarios would you choose one over the other?

Thanks very much!

---
#### Document Details

⚠ *Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.*

* ID: 19862882-c106-afa7-660e-ead3b5dd880a
* Version Independent ID: fea4a2d6-8aa5-a400-4261-6098e76d362b
* Content: [Challenges and solutions for distributed data management](https://docs.microsoft.com/en-us/dotnet/architecture/microservices/architect-microservice-container-applications/distributed-data-management)
* Content Source: [docs/architecture/microservices/architect-microservice-container-applications/distributed-data-management.md](https://github.com/dotnet/docs/blob/master/docs/architecture/microservices/architect-microservice-container-applications/distributed-data-management.md)
* Product: **dotnet-architecture**
* Technology: **microservices**
* GitHub Login: @nishanil
* Microsoft Alias: **nanil**