Well, don't write a simple wrapper. But don't sprinkle your entire codebase with nhibernate references either.
The domain model and major business logic should be as independent as possible of external dependencies. One might use the repository pattern, with the repository implementation in a separate assembly, that do have direct use of nhibernate. Then of course, there may be nhibernate-isms "leaking" through, even when you don't have direct usage of the API. /Oskar 2010/7/12 <[email protected]>: > If you choose a product (g.e NHibernate) and put a new level of abstraction on > it, the only result will be a messy codebase and (pardon me) a true waste of > time. > > If you think one day you will have to change your Data Layer then : > - You didn't pick the right choice > - Your selection process is not sufficient > - You will lose time doing technical staff that give very little added value > to > your developpement. > - You will face performance issues (the house that jack built syndrom) > > There is no such thinh as the ultimate reusable component because it is by > design a bad idea. > > In the Java world, it is called JDO,JPA and EJB. Just take a tour, take a > look, > try to make your path through the 23 different frameworks required and the > maount of work required to simply do some very basic CRUD stuff and you will > get > a flavor of the subject. > > Putting a "level of abstraction" is never a good thing when building the > basements. It is just increasing the complexity while putting some real risk. > > If you can't explain why and how you choose your persistence layer, then > that's > where your real risk is. And it won't go away by saying "I can change if I > need > to". > > Sorry, > > Fred. > > > Selon deepucodemaker <[email protected]>: > >> Hello All, >> >> I would like to design a system/application using NHibernate. But I >> also want to so flexible that in future if I unplug the NHibernate and >> use ADO.NET Entity framework or other framework application should not >> crash. >> >> Can someone please send me links/videos so that i can design >> independent architecture for this purpose. >> >> I tried lot in google and understood NHibernate but there is no >> example which helps me to deisgn ultimate reusable component. >> >> Please do the needful >> >> Thanks >> >> -- >> You received this message because you are subscribed to the Google Groups >> "nhusers" group. >> To post to this group, send email to [email protected]. >> To unsubscribe from this group, send email to >> [email protected]. >> For more options, visit this group at >> http://groups.google.com/group/nhusers?hl=en. >> >> > > > -- > You received this message because you are subscribed to the Google Groups > "nhusers" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group at > http://groups.google.com/group/nhusers?hl=en. > > -- You received this message because you are subscribed to the Google Groups "nhusers" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.
