Search the practice set
126 questions, 454 terms and 400 topics in 20 areas.
24 results for “Content Delivery Networks”
Content Delivery Network
A geographically distributed cache that serves content from a location near the user instead of from the origin.
At-Least-Once Delivery
The guarantee that a message will be delivered, possibly more than once — the practical default in every distributed messaging system.
Delivery vs Maintainability
Choosing where to take deliberate shortcuts, based on which kinds of debt are cheap to repay and which compound.
CI/CD
Merging work continuously into a shared trunk with automated verification, and keeping every commit in a state that could be released.
Container Image
A layered, content-addressed filesystem bundle plus metadata, from which containers are instantiated — immutable by construction and identified by digest.
DORA Metrics
Four measures of software delivery performance — deployment frequency, lead time for change, change failure rate, and time to restore service.
Embedding
A dense numeric vector representing a piece of content, positioned so that semantically similar content sits nearby.
Layer 4 vs Layer 7 Load Balancing
Balancing on connection metadata (IP and port) versus on the content of the request (path, host, headers).
Netflix Open Connect
Netflix built its own CDN and placed appliances inside ISP networks, turning the most expensive part of its cost structure into hardware it controls.
Offset Management
How a consumer records its position in a stream, and the decision that determines whether processing is at-least-once or at-most-once.
Partition Tolerance
The ability to keep operating when the network drops or delays messages between nodes — not a choice, but a property of any system spanning more than one machine.
Server-Side Request Forgery
Inducing a server to make an HTTP request to an attacker-chosen destination, turning it into a proxy into networks and services the attacker cannot reach directly.
Stakeholder Analysis
Identifying who is affected by an architecture, what each of them needs from it, and how much influence they have over whether it proceeds.
Time to Market
How long it takes to get a capability in front of customers — often the constraint that dominates every other architectural quality.
Trunk-Based Development
All developers integrating small changes into a single shared branch at least daily, with long-lived branches avoided entirely.
Visibility Timeout
The period after a consumer receives a message during which it is hidden from other consumers, before it becomes available again for redelivery.
Content Delivery Networks
Edge caching, origin offload, spike absorption and dynamic content.
Delivery vs Maintainability
Fast in the cheap places, careful in the expensive ones.
CI/CD
Continuous integration and delivery, and the architecture that caps them.
Operating Models
How delivery, platform and governance functions fit together.
Release Strategies
Blue-green, canary, shadow and progressive delivery.
Value Streams
End-to-end delivery of an outcome, and where the waiting happens.
Webhooks
Push callbacks, signature verification, ordering and at-least-once delivery.