Hi Reynald,

Here's a practical example that might help you better visualize this: imagine that you have a screen that lists employees and allows the user to select one from the list to present a long form do edit his details. You'll have at least 2 aggregates to fetch the required data (one for the list and another one for the details) and possibly a lot of inputs/widgets for the UI. This might result in a very big viewstate, which can greatly affect your application's performance.

In this scenario, adopting the suggested best practice would mean splitting this into 2 different screens. The first one lists the employees. When the user selects one of them, he's redirected to a different screen where he can edit the details.

I hope this helps illustrate what this suggested best practice is about.