On Mon, Aug 16, 2010 at 2:52 PM, Chad Sollis <[email protected]> wrote: > Quite honestly, doctrines performance issues concern me, but from generally > what I find online is that doctrine is the most functional ORM. > > For this heavy DB usage (not so much triggers/procs) SaaS solution. You would > still recommend orm, because of the advantages of the domain model?
Generally performance issues can be found in the lazy loading of your relationships. Meaning that instead of possibly running a single SQL Query with a JOIN ORMs tend to run two separate queries to generate the objects needed. If, and only if, you run into performance issues around lazy loading you can easily modify your model to use a different approach. Also they tend to guide you into putting more of processing into your application instead of the database. Things like date/time and other calculations that could be done in the database. Previous though over the years has been put as much logic in your database as possible because the database is designed and tuned to do that stuff better than your application. However in recent times use patterns generally show that performance bottlenecks often show up in the database itself. Databases can be difficult to scale horizontally, while applications (especially web applications) are incredibly easy to scale horizontally. _______________________________________________ UPHPU mailing list [email protected] http://uphpu.org/mailman/listinfo/uphpu IRC: #uphpu on irc.freenode.net
