A simple architecture is perfect for a simple application. But, as the application grows in its complexity, the architecture must become more complex in order to prevent it from becoming unmaintainable.
In this talk we discuss some ideas for simplifying complex code bases.
We also discuss the important distinctions between presentation, service, and domain layers and strategies for separating high-level business policy from implementation.
Some Domain-Driven Design topics are discussed, but this is not a talk about DDD. DDD is not about design patterns, but rather is about business analysis, communication, and much more.