The consequences of which pattern are:

1. Allows you to define hierarchies consisting of simple and complex objects. Simple objects can be composed into complex objects, which can also be combined with each other, etc. In the client code, wherever a simple object is expected, a complex object can also be provided.

2. Simplifies clients' code. Customers can treat complex structures and individual objects in the same way. Typically, clients cannot tell whether they are using a leaf or a compound component (and it shouldn't matter). This simplifies client code because you don't have to write complicated functions that check the classes that define the assemblies.