Architecting Applications for the Real World in .NET
Pluralsight
Course Summary
An architect's job is to manage 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? Viewers will learn when abstractions are justified and walk away with an understanding of the merits of various approaches for structuring the business, service, presentation and data access layers with a pragmatic, real-world mind set.
-
+
Course Description
An architect's job is to manage 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? This course discusses when abstractions are justified and outlines the merits of various approaches for structuring applications with a pragmatic, real-world mind set. The discussion begins by outlining philosophies for thinking about architecture and considering the benefits of doing the simplest thing that could possibly work. Then we dive into various design patterns and technologies to consider within the business, service, presentation and data access layers. And in the final capstone module we'll consider two specific architectures and discuss the contexts where each makes sense. You'll learn when table module, active record, DDD, and ORMs are useful and walk away with the tools to better evaluate and justify complexity as an agile software craftsman. Like any responsible architect, we'l focus on the value of keeping things simple whenever we can.
-
+
Course Syllabus
Introduction and Agenda- 7m 13s
—Introduction 2m 32s
—Pragmatic Architecture 2m 56s
—Agenda & References 1m 44sReal-World Architectural Thinking- 25m 57s
—Two Approaches: Which is Better? 3m 57s
—Metaphors for Architecture Selection 3m 49s
—Considering Complexity 2m 47s
—The Argument for Simplicity 9m 4s
—Time-line Impacts on Architecture 5m 20s
—Summary 0m 58sBusiness Logic Layer- 31m 25sService Layer- 21m 40sPresentation Layer- 19m 49sData Access Layer- 39m 35sArchitectural Levels- 27m 12s