Timeline for Service layer vs DAO -- Why both?
Current License: CC BY-SA 3.0
4 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 12, 2017 at 7:31 | history | edited | CommunityBot |
replaced http://programmers.stackexchange.com/ with https://softwareengineering.stackexchange.com/
|
|
| Dec 11, 2013 at 11:09 | comment | added | Jesus | @LennyGodber yes, I know your feeling IMO is better to have the DAO/repository layer because as it has more advantages that disadvantages because as you were saying it is very common to have multiple data sources | |
| Dec 11, 2013 at 9:47 | comment | added | Mr Cochese | I've read Ayende's blog post multiple times now, and just cannot shake the feeling that his design (which I would have agreed with at one point), while true to the spirit of YAGNI, would almost inevitably cost more dev time in even the medium term than it would cost to set up the abstraction of layers in the first place. I wonder if he has changed his opinion on tight coupling between the entire application and NHibernate now that it's even more common for a single application to query multiple SQL, NoSQL and API data sources. | |
| Dec 10, 2013 at 16:33 | history | answered | Jesus | CC BY-SA 3.0 |