Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I want to start building better persistence layers using NHibernate and other ORMs. What are the best design patterns or important design considerations for implementing persistence with ORM?
Couple off the top of my head…
1) Be careful not to group data that changes at drastically different rates into the same object. This can end up bloating tables with redundant data.
2) Avoid throwing in text fields that you intend to search, better to use something like Lucene for this. DBs aren’t as efficient as dedicated text search libraries when doing LIKE style queries.
3) If you can make it so that your objects are immutable once written (i.e. they have a state id), then you can get very nice caching benefits on the front end and keep people from even needing to hit your server in the first place.