Your framework choices strongly influence the architecture your applications will have. Many of the architectural decisions have already been made by the framework for you, so trying to impose your own architecture over that would be like swimming against the current.
But this is kind of the whole point of choosing a framework. Developing a suitable architecture for your application can be tedious when you have to standdesign and build the whole thing up by handyourself.
In practice, unless I'm writing my own framework, I don't like to think all that much about the architecture. Architecture should be something that's just a part of the fabric of your application, not an end in its own right, and if you use a framework that you like that does all of the architectural heavy-lifting for you, so much the better. It means that you spend more time developing actual functionality and less time putting in plumbing.
If you're going to go this route, you have to think carefully about your framework choices and how each one fulfills its role of helping you build your application. But choosing a framework because it is a "quick and dirty" way to get an application working is a perfectly valid choice. It all depends on what your actual needs are.