Beyond Good and ORMs
summary
Argues that ORMs hide built‑in database features and shows concrete alternatives: create database views to replace expensive joins (example: 50 restaurants returning 160 objects versus a view returning 50 rows), use materialized views for nightly reports, put logging and data transformation into stored procedures and triggers to avoid round trips, and exploit Postgres types like array data type, hstore/json, ranges, enums, UUIDs and geospatial functions. Claims Postgres can be an order of magnitude faster (roughly 100ms → 10ms) and ActiveRecord can map to these DB objects.
AI-written summary · about
chapters (11)
- 0:00Start
- 2:35Shifting Viewpoint
- 17:12Materialized Views
- 18:29The Rabbit Duck
- 19:44Functional Fixedness
- 22:07Stored Procedures
- 24:08Postgres
- 25:43Triggers
- 27:10Active Record Data Types
- 35:22Enums
- 35:50Ip Addresses
related talks
23mI Would Never Use an ORM
01h 01mNew Approach to Resolve objectrelational impedance mismatch
25mI Would Never Use an ORM
46mUse PostgreSQL, not Rails, to make Rails Faster!
31mUsing Databases to pull your applications weight
43mJust Use Postgres.
41mApplication Development Challenges with Postgres
41mUsing Databases to Pull Your Application Weight