Q. DTO Consolidation and Change Propagation in Microservices

1. Is consolidating DTOs a common or necessary practice when fetching consolidated data from multiple microservices?
We only had three services, and even that felt quite cumbersome and error-prone.
I don't know what I will do if I have more than 10 services.

2. What happens when a DTO or an entity within one of the microservices changes?
For example, if we have a `Customer` service and its DTO has an `address` field, what is the impact if the data type of this field changes?
- Original DTO: `CustomerDto` includes `String address`
- New DTO: The team decides to use a more structured object for the address, so `CustomerDto` is updated to include an `AddressDto address`, where `AddressDto` contains fields like `street`, `city`, and `postalCode`.
Does this change cascade and force us to update the consolidated DTO and the corresponding endpoint?