Frameworks solve common problems, and thus allow rapid application development. Agile and incremental software development, however, does not magically create architectures as you go. We will prove the point that your favourite framework does not provide you with an application architecture, and analyze what implications this has. This talk is not about big design up front, and not about "your framework is bad", or "another framework is better". It is about avoiding to end up in a situation where software works, but maintenance is tough, expensive, and bears more risks than you can afford to take, regardless of which framework you are using.