Timeline for Repository Pattern with Multiple ORM
Current License: CC BY-SA 3.0
7 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Nov 4, 2016 at 16:36 | comment | added | Doc Brown | @dan1111: indeed, Dropbox was just one year old and not out of its beta phase at 2008, when Joel wrote that article. | |
| Nov 4, 2016 at 15:13 | comment | added | Ram kumar | @Jon, Any implementations on abstract ORM. Or I can create Repository Layer which will have entities,Interfaces, Repository impelentations where the repository will use DTO(which entity is convert as model and vice versa) | |
| Nov 4, 2016 at 15:08 | comment | added | Jon Raynor | @Ram - Well my pragmatic answer aside, you would have to build out another abstraction so that the ORM is abstracted away. Maybe an interface called IObjectRelationTool to start with. Then you would have a EF tool implementation and a nHibernate tool implementation. | |
| Nov 4, 2016 at 15:00 | comment | added | Ram kumar | @Jon, Its is multi tenant application so it can change to nhibernate, So any ideas on the implementation. Models will not change only instead of EFUOW and EFRepository i need to use NHUOW and NHRepository | |
| Nov 4, 2016 at 14:45 | comment | added | user82096 | @DocBrown I agree. Though it's amusing that Joel's example of a stupid thing that nobody needs is cloud-based, accessible-anywhere file storage. | |
| Nov 4, 2016 at 14:38 | comment | added | Doc Brown | Exactly my thoughts, building a system to switch between ORMs looks more like a task for an architecture astronaut | |
| Nov 4, 2016 at 14:32 | history | answered | Jon Raynor | CC BY-SA 3.0 |