New Approach to Resolve objectrelational impedance mismatch
summary
Shows concrete wins: Ruby on Rails with Active Record and Postgres is generating 1,000 database calls per screen for some controllers, identified by PG Badger as top offenders (one query runs ~500k times and totals hours). The approach is to split logic—disassemble methods, build a single Postgres query or function, and validate with dark testing—cutting calls to ~1–5 and reducing execution time about threefold.
AI-written summary · about
chapters (9)
- 0:00Intro
- 2:03Database Application Performance
- 13:33What is Impedance Mismatch?
- 18:02Development Standards & Performance
- 31:40Logic Split Methodology
- 38:03Under the Hood: Database Calls
- 44:26Traditional Object-Oriented Approach
- 54:23Agile Technology
- 58:19Aknowledgements
related talks
42mHolistic Database Application Tuning
26mBiggish Data With Rails and Postgresql
46mUse PostgreSQL, not Rails, to make Rails Faster!
31mUsing Databases to pull your applications weight
30mPuny to Powerful PostgreSQL Rails Apps
41mUsing Databases to Pull Your Application Weight
46mBeyond Good and ORMs
34mBeyond CRUD: the PostgreSQL techniques your Rails app is missing.
