No, there generally aren't master architects. I'm surprised to hear you talking about master architects, in traditional programming circles the term is usually met with scorn. There's a perception that people who call themselves architects or talk about architecture tend to suck at programming. That they like talking about code, but in general are not actually capable of doing it.
Hearing someone say they're a software architect or that a company has a software architect is usually a big red flag to run like hell.
Also a large code base is identical to a complex problem. Check the definition of complexity. A complex problem can be broken down into simple components.
Finally the best glue is not complex, it's simple. Complex glue tends to result in brittle magic, a poor abstraction, like traditional asp.net compared to something far more elegant and smaller like ruby on rails.
Hearing someone say they're a software architect or that a company has a software architect is usually a big red flag to run like hell.
Also a large code base is identical to a complex problem. Check the definition of complexity. A complex problem can be broken down into simple components.
Finally the best glue is not complex, it's simple. Complex glue tends to result in brittle magic, a poor abstraction, like traditional asp.net compared to something far more elegant and smaller like ruby on rails.