Practical Application Architecture with Entity Framework Core

Learn how to choose an application architecture to use with Entity Framework Core for several different scenarios.

To get the most out of Entity Framework Core—a cross-platform way to access data from an application—it's important to know how to make sound architectural choices. In this course, learn how to choose an application architecture to use with Entity Framework Core for several different scenarios. Richard Goforth covers why all of this architecture is necessary, and dives into design patterns with Entity Framework Core, discussing topics such as data access layers, DTOs, and exposing the queryable interface from Entity Framework Core. He also goes into error handling strategies, architectural strategies for using Entity Framework Core within ASP.NET, unit testing, and mistakes to avoid when architecting software with Entity Framework Core.

Introduction

• Welcome
• What you need to know
• What is good application architecture?
• How to use the exercise files

1. Why Do All of This Architecture?

• Real-world software and the SDLC
• Multi-layer applications
• Multiple applications and tiers
• Common knowledge and maintenance
• Choosing an architecture

2. Design Patterns with EF

• Data access layer
• Repository
• Unit of work
• Inversion of control
• Queryable
• DTOs
• Command query

3. Error Handling

• Matching the model to the data
• Debugging errors
• DbUpdateException
• Concurrency handling

4. Architecture for the Web with ASP.NET

• Scoping and memory usage
• Caching
• Validating data
• View model mapping

5. Designing for Unit Testing

• Decoupling
• InMemory database provider
• Mocking objects
• Testing business logic in queries
• Common testing mistakes

6. Entity Framework Mistakes

• Data models everywhere
• Unnecessary layers
• Poor performance

Conclusion

• Next steps