I’ve been using ORM for more than a year. I was fascinated over the project development speed by using ORM. After using for a year we found that it is so damn slow comparing to a direct .Net Ado call. We did sample test after getting complaints from the users about our projects degrading performance, and found that ORM (Olero version) was unforgivably slow.
I suggest that before using Olero ORM for your project, do a sample CRUD test application with ORM, Direct Ado and with any other middle tire option that you have. Go through about 1000 record reads, 100+ updates etc.
Well, i'm paying the price now by re-coding from square one.
Cheers
Krishan Ariyawansa
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Don't scare me. Is it really that bad? I'm just about to get started. Doesn't ORM.NET support stored procedures? So if you have some efficient query and update logic, you can easily call them.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Good day,
I’ve been using ORM for more than a year. I was fascinated over the project development speed by using ORM. After using for a year we found that it is so damn slow comparing to a direct .Net Ado call. We did sample test after getting complaints from the users about our projects degrading performance, and found that ORM (Olero version) was unforgivably slow.
I suggest that before using Olero ORM for your project, do a sample CRUD test application with ORM, Direct Ado and with any other middle tire option that you have. Go through about 1000 record reads, 100+ updates etc.
Well, i'm paying the price now by re-coding from square one.
Cheers
Krishan Ariyawansa
Don't scare me. Is it really that bad? I'm just about to get started. Doesn't ORM.NET support stored procedures? So if you have some efficient query and update logic, you can easily call them.