Day 1: Anonymous Block (DO $$) & The Chatty Application Anti-Pattern
Learn PL/pgSQL DO blocks and why chatty apps lose to in-database logic.
View Day 1 →Push work into the database and stop paying for chatty round-trips
Learn PL/pgSQL DO blocks and why chatty apps lose to in-database logic.
View Day 1 →Keep logic next to 8KB pages in shared buffers so PL/pgSQL wins over chatty round-trips.
View Day 2 →Idle-in-transaction, lock wait, and deadlock: the concurrency cost of holding a lock while the app talks over the network.
View Day 3 →Phase 1 checkpoint: turn the chatty-app vs in-database map into a slide narrative.
View Day 4 →Move logic into PostgreSQL UDFs and understand inlining mechanics.
View Day 5 →COMMIT and ROLLBACK inside procedures so chunked batch work releases locks safely.
View Day 6 →Catch schema and data events inside the database and write an audit trail.
View Day 7 →Precompute heavy dashboards and refresh them concurrently on a schedule.
View Day 8 →Drop RBAR loops, think in sets, and let PostgreSQL use multiple cores.
View Day 9 →Close Phase 2 of the 18-day masterclass before entering DevOps and architectural boundaries.
View Day 10 →Versioned vs repeatable migrations, schema drift detection, and CI/CD for stored units.
View Day 11 →Shift-left database unit tests with pgTAP, ephemeral Testcontainers, and transactional isolation.
View Day 12 →Keep CPU-bound work in the app and data-bound work in PostgreSQL so the database CPU stays protected.
View Day 13 →Compare trade-offs and the anti-patterns that break in-database automation, including cascading triggers and unsanitized dynamic SQL.
View Day 14 →Turn the architecture into a proposal and tech spec you can pitch to the software team.
View Day 15 →