Activerecord uses an enormous amount of resources that the databasr is way better equipped to handle, unfortunately. There is also a mindset problem that's pre

Activerecord uses an enormous amount of resources that the databasr is way better equipped to handle, unfortunately. There is also a mindset problem that's pretty serious in the ruby world, developers would use activerecord and load the universe, rather than running a select query carefully narrowed to the specific needs. on top of this, often there are entities that are the result of joining tables, but these are never surfaced with ORMs (activerecord specifically), since the concept of an entity from a query joined with multiple tables doesn't exist except in the limited fashion of a view.