Using an object relational mapper, ORM, is a good idea if you have an object relational code base and are following standards. By using an ORM you get a separation between actual objects and data persistence. This also makes it possible for the programmer to fully focus on the application without knowing much about how the database itself works. However, this doesn’t come without drawbacks. Depending what ORM you use and how you use it, it may sacrifice performance. The research in this thesis shows that using an ORM in a very small application does not sacrifice performance.
| Identifer | oai:union.ndltd.org:UPSALLA1/oai:DiVA.org:lnu-12623 |
| Date | January 2011 |
| Creators | Sanver, Michelle |
| Publisher | Linnéuniversitetet, Institutionen för datavetenskap, fysik och matematik, DFM |
| Source Sets | DiVA Archive at Upsalla University |
| Language | English |
| Detected Language | English |
| Type | Student thesis, info:eu-repo/semantics/bachelorThesis, text |
| Format | application/pdf |
| Rights | info:eu-repo/semantics/openAccess |
Page generated in 0.0022 seconds