The question does not really make much sense. Architectural solution does not mean looking at some list of available architecture type and choosing one. Architecture is something you have to build; and this work depends on many factors: goals of the programming system, requirements, available resource, sometimes, even on the personal skills and preferences of the team members.
From the other hand, you can use some available
architectural patterns. But this is not the same as "architectural type". This is something you can embrace in your architecture, in different degrees of comprehensiveness; sometimes, you can use only some of the idea. But MVC is already one of such patterns.
See also:
http://en.wikipedia.org/wiki/Model%E2%80%93view%E2%80%93controller[
^],
http://en.wikipedia.org/wiki/Software_design_pattern[
^],
http://en.wikipedia.org/wiki/Architectural_pattern_%28computer_science%29[
^].
—SA
Submit an article or tip