MSAMM
Back to course

Oracle Visual Builder: Applications That Outlive Their First Release · Module 15 · Performance

Caching, and when it lies

Lesson 153 of 176 · 3 min

HOLDING DATA TO AVOID A CALL, and THE STALE VALUE SOMEBODY ACTED ON. Caching is the most effective performance fix and the only one in this module that can make an application WRONG rather than merely slow. THE TRADE IS EXPLICIT: YOU ARE EXCHANGING FRESHNESS FOR SPEED. Every cached value is a value that may have changed since you fetched it, and the question is never whether it can go stale — it is what happens when it does. WHICH IS WHY REFERENCE DATA IS THE SAFE CASE AND ALMOST THE ONLY ONE. A list of countries, statuses, categories. It changes rarely, everybody sees the same values, and being a day out is usually harmless — Lesson 3's repeated lookups, and the legitimate place to hold something. AND TRANSACTIONAL DATA IS THE DANGEROUS CASE. A balance, a status, an amount — anything somebody else can change while this user is

The full lesson is part of the course

The video, the complete written lesson and the module quiz are included in Oracle Visual Builder: Applications That Outlive Their First Release, with a certificate on completion and a fourteen-day refund window.

Get the free lessons by email

We will email you a link to every free lesson in this course. No account needed, and one message only.

In this module: Module 15 · Performance

  1. 1Measure before you change anything
  2. 2Over-fetching: the usual cause
  3. 3Too many calls
  4. 4Rendering a large list
  5. 5What to load, and when
  6. 6Caching, and when it lies
  7. 7What breaks: three performance failures
  8. 8Lab briefing · Ten times the data