An architect’s job is to reduce complexity, not increase it. Yet the developer life is filled with jargon, acronyms, and seemingly infinite choices. So how do we know when complexity makes sense? Let’s discuss when abstractions are justified and determine how to structure applications so they’re maintainable, scalable, and testable. We’ll make sure everyone is comfy with the core jargon like N-Teir, separation of concerns, and loose coupling. Then we’ll dive into various patterns for implementing the three common layers using various .Net technologies. You’ll learn when table module, active record, DDD, and ORMs make sense and walk away with the tools to better evaluate and justify complexity as an agile software craftsman. We’ll focus on the value of keeping things simple whenever we can.