Lean Enterprise Architecture
Download as PPTX, PDF4 likes7,425 views
The document discusses a lean, modernized approach to enterprise architecture using ASP.NET MVC and Entity Framework with a focus on test-driven development, code-first migrations, and continuous integration. It outlines the goals and workflows involved in implementing a data access layer, including model mapping and database updates. Best practices and resources for development teams are also provided, emphasizing simplified architecture over complex designs.
Lean Enterprise Architecture
- 1. Lean Enterprise Architecture By Shahed Chowdhuri, Sahil Talwar, Doguhan Uluca A lean, testable enterprise architecture with a modern client stack
- 2. Thanks to our Sponsors for keeping the fires lit
- 3. TDD (Test Driven Development) BDD (Behavior Driven Development) CI (Continuous Integration) CD (Continuous Delivery) Introduction ASP.NET MVC DB Enterprise Web Application Looking for Ways to Improve & Modernize Motivation behind this design? Our desire to do the following:
- 4. Data Access Layer Shahed ChowdhuriUsing Code-First Migrations
- 5. Tech Check ASP .NET MVC Entity Framework EF Code-First Development EF Code-First Migrations Are you familiar with…?
- 7. What are we trying to solve?
- 8. DAL: Agenda 1. Models & Mapping 2. Connection Strings 3. Enable Migrations 4. Update Database 5. Push Code + Migrate Server DB 6. Process Workflow
- 9. 1. Models & Mapping DBContext .OnModelCreating()
- 12. migration code 4. Update Database model code migration code + seed dev DB (sql)
- 13. 5. Push Code + Migrate Server DB code push code CI code pull code migrate.exe Server DB
- 14. 6. Process Workflow dev team DB architects communication DB
- 15. Code Walkthrough
- 17. Resources • EF Code First Migrations on MSDN: – http://msdn.microsoft.com/en-US/data/jj591621 • Web.config & configSource: – http://wakeupandcode.com/all-your-database-are-belong-to-us/ • PluralSight EF Migrations video tutorial: – http://pluralsight.com/training/Courses/TableOfContents/efmigrations
- 18. The Domain Sahil Talwar Simpler is better
- 22. Versus…
- 24. Round
- 25. Best Practices Repositories Unit of Work Entity Framework
- 26. Domain IUnitOfWork IRepository IRepository IRepository Dal DbContext DbSet DbSet DbSet Web Api
- 28. Round
- 29. Web Models Domain Models Dal Models Api Models
- 32. Round
- 33. Student Context Universities Departments Professors Classes Advisors Students Context Per Complex Object University Context
- 34. Professors Classes Students Departments Advisors Universities Single Responsibility: Context Per Object Universities Departments Professors Classes Advisors Students
- 35. ServiceStoreServiceStore Service Service Service Shared Context Service Service Service
- 36. Solid gold.
- 37. Services Domain 1 Web Api Domain 2 Domain 4 Domain 5 Dal Models Domain 3 Domain 6
- 40. Image Credits • http://i-cdn.apartmenttherapy.com/uimages/kitchen/2010_05_17-Lasagna.jpg • http://www.callagold.com/wp-content/uploads/2012/02/gold-plated-porsche-1.jpg • http://img.diytrade.com/cdimg/1057186/11295732/0/1259756915/Gold_Plating_System.jpg • http://www.artisticplating.net/images/gold4.jpg • http://epf.thingml.org/wikis/inf5120/practice.mgmt.scrum.base- sintef/guidances/roadmaps/resources/ScrumLargeLabelled.png • http://1.bp.blogspot.com/-H0OeuWi6oXc/UG9BbClJF- I/AAAAAAAAAqY/6v4hZ5zGGXk/s1600/DDD_TDD_BDD_intersection.png • http://blogs.jetbrains.com/teamcity/wp-content/uploads/2008/09/teamcity512.png • http://www.regretfreelife.net/wp-content/uploads/2012/09/lscycle.jpg • http://automapper.org/img/black_logo.png • http://4.bp.blogspot.com/-1p7GSp6m_a8/UOrbvzLfwKI/AAAAAAAAAI4/oYULEv-jJWc/s1600/g3211.png • http://www.clker.com/cliparts/T/G/C/H/K/W/no-sign-hi.png • http://2.bp.blogspot.com/---z3- XY_a5M/T2uGslh4fYI/AAAAAAAAADY/PyqTk88n3Qo/s1600/Health+Services+Enterprise+Architecture+v5.3+( 3-20-12).jpg • http://fc06.deviantart.net/fs71/f/2012/119/e/7/sumo_wrestler_by_maxxparis-d4xytyj.jpg • http://www.nerdpad.com/wp-content/uploads/2010/04/vs2010_full.jpg • https://secure.gravatar.com/avatar/cf4c53b37956b009d609caeacb171c40?s=420&d=https://a248.e.akamai. net/assets.github.com%2Fimages%2Fgravatars%2Fgravatar-org-420.png • http://nblumhardt.com/wp-content/uploads/2009/12/Autofac-2-Sketch1.png
Editor's Notes
- #2: Lean Enterprise Architecture (title page)A lean, testable enterprise architecture with a modern client stack
- #3: Sponsors
- #4: Introduction* We are building an enterprise web application with ASP.NET MVC, following best practices for design, development, testability and deployment.* We were looking for ways to improve and modernize* The motivation behind this design was our desire to do TDD, BDD, CI, CD.
- #6: Are you familiar with:ASP.NET MVC?Entity Framework?Code First development?Code First Migrations?(slow-reveal diagram + ask the audience)
- #7: Options and AlternativesDatabase-First (EDMX)Model-First (visual designer)Code-First with automatic migrationsCode-First with manual migrations
- #9: AgendaAdd models and mapping in codeConnection StringEnable MigrationsUpdate DatabasePush code + Migrate server DBProcess Workflow
- #10: 1. Models & Mapping
- #11: 2. Connection StringsConnection StringWeb.configconfigSourceMachine config
- #12: 3. Enable MigrationsEnable MigrationsConfiguration.csAdd Seed data
- #13: 4. Update DatabaseUpdate DatabaseRun Seed DataVerify SQLVerify DB
- #14: 5. Push Code + Migrate Server DBPush code to source controlOther developers pull and Update DatabaseMigrate server DB via migrate.exeUse TeamCity to automate this
- #15: 6. Process WorkflowProcess WorkflowHandle existing databaseComply with enterprise requirements
- #16: Code Walkthrough
- #17: Code First Migrations allows:Continuous developmentSynchronization among team membersDatabase versioningServer deployment(diagram with star pattern)
- #18: Resources
- #19: IntroShahed showed DAL, so I’ll run through DomainFair warning, though…
- #20: This is not like the other two parts of the presentation!I won’t show you code…Or specific technologies…at all.Instead, war stories and lesson learned
- #21: Using Scrum,
- #22: CI, CD…TDD, BDD, and DDD…
- #23: But at the same time, some people involved with the project are proponents of…
- #24: HEAVYWEIGHT enterprise architecture.To see what I mean, compare layersJokes aside, 1 story of over-engineering causing problems:
- #26: When using DDD…blogsDev tried to use best practicesDidn’t check if we had the problems
- #27: 3 problems: Use of UoW optionalRedundant, as I saidTo top it off: buggy, slow, redundant
- #28: Now that’s what I call gold plating!
- #30: The second story of the day is about premature optimization. Knuth: “premature optimization is the root of all evil”Optimizing for unproven use case because app is complex, expensive, many dev teamsAutomapper both waysWhat does Bogard know? Wrote != knows domain!
- #31: Eventually realized it was gold plating as much as the Repositories were
- #32: After unreasonable time, came to our sensesPulled out model into cross cutting layerNo more automapper!!Api has Data Contracts that look nothing like models, so that is a valid exception.
- #33: Re: sharing a database context across objects.
- #34: Service for every complex objectInjected new DbContext into every serviceProblem with shared sub-objects being accessible in several contexts
- #35: Looked to SRP for guidance one per objectNot only does not solve issue, makes it worse by making nearly all db objects sharedAlso creates Repo explosion
- #36: Made a store to manage # of servicesRealized shared context problem, this fixes it# of Services = pain to manage and test!Came to realizetoo many services & shared context problemsStore was messy, painful hack
- #37: Basically, realized that this is a step beyond gold plating.This is solid gold.
- #38: Solved problem by splitting up into non-overlapping domains. Practically, this means 1 service per project team, & no overlapping objects.Anyone heard of bounded contexts…?Original solution proposed by DDD to begin with.Anyway,
- #39: We fought against over-engineering and gold plating by using lean startup principles:BuiltMeasured pain; demonstrated to EA proponentsLearned from mistakes, built a solution closer to what we believed would alleviate the problemsRinse & Repeat