MSDN Ramp-Up Part 3: Business logic
Download as PPTX, PDF0 likes995 views
The document discusses best practices for implementing business logic in applications, focusing on the separation of concerns in different layers such as the UI, data access, and business logic layers. It highlights the importance of using Object-Relational Mappers (ORMs) like Entity Framework and discusses patterns and anti-patterns related to business logic structure. The document emphasizes principles like single responsibility, extensibility, and testability for developing better-designed applications.
MSDN Ramp-Up Part 3: Business logic
- 1. Business LogicFrom btn_Click to business layersJon LimjapSenior Developer for ITRSMVP for C#
- 2. AgendaWhere we left offCommon patterns and anti-patterns of business logicWhich ORM do I use?Towards a better designed application
- 3. Where we left offEntity Framework and other ORMs
- 4. Entity Framework (and other ORMs, really)
- 5. Why is this important?Separation of concernsReuse of data access methods across different business rule implementationsCentralized management of connection pools, data caching possibilities, etc.
- 6. Common patterns and anti-patterns of Business LogicHow business logic is strewn across your application
- 7. Business Logic (and data access) in the UI layerUser Interface/Data Access/Business LogicBusiness Logic and data access in click events, UI Data Providers, etc.Big Ball of MudRelational Database
- 8. Business Logic in the Data LayerUser InterfaceMay or may not be presentData Access LayerRelational DatabaseBusiness Logic in stored procedures
- 9. Business logic separate from data and UIUser InterfaceBusiness Logic LayerEntity Framework, Nhibernate, LINQ to SQL, ADO, etc.Data Access LayerRelational Database
- 10. Business logic in the cloudHTTPHosting/HTTP ListenerData Services RuntimeBusiness Logic LayerData Access LayerRelational Database
- 11. Which ORM do I use?If there’s very little difference between ORM’s anyway…
- 12. ConsiderationsDatabase First: Generate model from existing databaseModel First: Create your model and generate your databaseCode First: In-memory mapping (EF only)
- 13. Summary
- 14. Towards a better designed applicationWhy bother going down this path
- 15. Why should I bother?Single Responsibility Principle Change in once place fix everywhereExtensibilityTestability
- 16. What do I do now?No need to change existing setup – unless you’ve decided to rewrite everythingBaby stepsFor new features, code new layers in a “thin vertical slice”Expand only as needed
- 17. Further Reading