Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
24 results for “Rendering Strategies”
Render Location Decision
Where HTML is produced — build time, server, edge or browser — chosen per route by how personalised and how cacheable that route is.
Join Strategies
The three ways a database combines two row sets — nested loop, hash join and merge join — and the conditions under which each is correct.
Bloom Filter Cache Guard
Placing a Bloom filter in front of an expensive lookup so that keys which certainly do not exist never reach it.
Blue-Green Database Schema
The constraint that makes fast rollback actually work — both application versions must be able to run against one schema at the same time.
Client Runtime Constraint
The properties of the browser or device you do not control — CPU, network, version, extensions — which make the client a distributed system component rather than a rendering surface.
Dual Write
Writing the same change to both the old and new stores during a migration, and the reconciliation that makes it trustworthy.
Edge Personalisation
Varying a cached response at the edge on a small number of attributes, so the page stays cacheable while still differing per visitor segment.
Immutable Backup
A backup that cannot be modified or deleted for a defined retention period, even by an administrator — the control that makes backups survive ransomware and insider error.
Locale Aware Formatting
Rendering dates, numbers, currencies and names according to the user's locale rather than the developer's, using the platform rather than hand-written logic.
Point-in-Time Recovery
Restoring a database to any moment within a retention window by replaying transaction logs onto a base backup, rather than only to a snapshot boundary.
Restore Drill
A scheduled, timed exercise of restoring from backup into a clean environment — the only thing that converts a backup from a hope into a control.
Rolling Update Surge
The extra capacity a rolling deployment temporarily adds, and the unavailability it is permitted, which together decide whether the rollout is safe under load.
Six Rs of Migration
The standard menu of options for each application in a migration — rehost, replatform, refactor, repurchase, retire, retain.
Testing Strategy Shape
The distribution of tests across levels, chosen so that feedback is fast where it can be and confidence is real where it must be.
A marketing site is a client-rendered single-page application. Organic traffic is poor and the team blames the search engine. What is your assessment?
The rendering choice is the problem A marketing page is identical for every visitor and highly cacheable. Rendering it in the browser pays for personalisation t
A team says "backups run nightly and are retained for 30 days". You have one hour to assess whether they could actually recover. What do you check?
The checks, in the order that finds problems fastest 1. When was a restore last performed, and how long did it take? The single most informative question. If th
Rendering Strategies
Client, server, static and incremental rendering, and what each costs on first paint.
Backup Strategies
Scope, immutability, separation, and the restore drill that makes it real.
Caching Strategies
Cache-aside, read-through, write-through and where each belongs.
Data Migration Strategies
Backfill, dual-write, reconciliation and verification.
Deployment Strategies
Rolling, blue-green, canary and shadow, and the traffic and state each one assumes.
Edge Rendering
Running the render close to the user, and the personalisation and cache trade it implies.
Release Strategies
Blue-green, canary, shadow and progressive delivery.
Testing Strategies
The pyramid, and the contract tests distributed systems add to it.