PUBLIC MARKS with tags architecture & "design pattern"

I've spent some time thinking about how a web application should be architected. How should it look from a high level? How does the development cycle look? How does the deployment process look? I read a lot about how applications should be modular, and I agree with this, but in practice I've come to realize I don't know how a large application should look.

Design patterns are just for Java™ architects -- at least that's what you may have been led to believe. In fact, design patterns are useful for everyone. If these tools aren't exclusive to architecture astronauts, what are they, and why are they useful in PHP applications? This article explains.