How are admin panels implemented in microservice architecture?

Question

Software design

Here is a hypothetical project implemented in the form of several microservices. Let it be a shop. Separate service for user accounts, separate for orders, separate for inventory control - each has a separate database, all exchange domain events and maintain final consistency. But, at the same time, there are managers who provide aggregated statistics with sorting and filtering. How, in this case, are the admin panels implemented in the microservice architecture, because you don’t have to run around all the individual databases collecting the necessary data?

Answer 1

I will answer myself:
1. Run through microservices and collect data from them through their API for display in the admin panel.
+ strict consistency
- slow
2. Create a separate database (Base), in the bark in a denormalized form to store all the necessary data together. Update data in the Database when microservices change. Build an admin panel based on this Base.
+ fast
- final consistency (not the fact that at the time of the request the situation will be exactly the same as it is presented in a single database)
3. Mix both methods. Get something from the common database, go directly to the services for something.

Answer 2

API