As a software architect or designer, you should be able to read, understand, and apply these models in the context of engagement requirements. One would able to determine if a particular pattern applies to the context in which you are architecting and whether the stated problem exists in your proposed system. You can then follow the pattern and apply it in your particular context.
This is not about a particular technology specification, such as Microsoft's .NET, Oracle's JEE, or a particular product set, such as the Oracle Application Server. This is a conceptual view of systems that we're interested in and how architectural components of the system are arranged. Where appropriate, we have described how a particular technology, platform, or product supports the general concepts. This includes the idea of the relative cost of different solutions since, as a software architect, you will almost certainly become involved in brainstorming...