we are building a system that will have very high concurrencies.
For optimization sake, we are thinking about only using Stored Procedures, instead of simplifying our life with an ORM.
Is it a good thing to do?
Is there any ORM out there that are really worth it performance wise, with a very low footprint?
分享 I don't think you'll find a general answer.
An ORM can be as simple as a few lines of code or as complex as the monstrosity that is Doctrine.
Performance wise, I'm not sure you'll see much difference between using stored procedures and an ORM whose back-end uses prepared statements. It's probably worth benchmarking to find out.
However, from a maintainability point of view, Take, for example, the addition of a field in a table. In an ORM this could be as simple as a single file edit. With stored procedures it can mean updating a lot of stored procedures to account for it.
An ORM gives more flexibility as it doesn't tie all your data to the database and gives you more portability moving forwards. Of course it's weighing these benefits to whether you think they're worthwhile.
That said, there's nothing to stop an ORM calling stored procedures either.
分享
