Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
51 results for “Edge Functions”
Cold Start at the Edge
The initialisation delay when a request reaches a location with no warm instance, which at the edge occurs far more often because traffic is spread across many locations.
Edge Aggregation
Summarising or filtering telemetry at the device or gateway so that only what is needed leaves, which is usually the difference between a viable and an unaffordable design.
Edge Function
Code executed at a CDN point of presence close to the user, in a constrained, fast-starting runtime, typically to modify or route a request before it reaches an origin.
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.
Admission Control
Deciding at the edge whether to accept a request at all, based on current capacity, before any work is done on it.
Automated Governance
Encoding architectural rules as executable checks in the build pipeline, so conformance is verified continuously rather than reviewed periodically.
Compute Tier Placement
Deciding which of on-device, on-premises, metro, regional or central compute a workload belongs to, from its latency, data volume and autonomy requirements.
Content Delivery Network
A geographically distributed cache that serves content from a location near the user instead of from the origin.
DAG Dependency
The declared edge stating that one task must not start until another has succeeded, and the difference between that and merely running later.
Definition of Done
The agreed, explicit conditions under which work is finished, which functions as a quality gate only when it is automated and non-negotiable.
Evolutionary Architecture
Designing for guided, incremental change rather than trying to get the structure right once, up front.
Global Traffic Management
The layer that decides which region a given user reaches, using DNS, anycast or an edge network, and that performs regional failover.
Origin Shield
An intermediate caching layer between CDN edge nodes and the origin, so a cache miss at many edges results in one origin request rather than many.
Read Local Write Global
Replicating read-only state to every edge location while directing writes to a single authoritative region, which is the arrangement most edge data stores actually provide.
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.
Reverse Proxy
A server that receives client requests on behalf of one or more backends, forwarding them and returning the response.
Secure Boot Chain
Each boot stage verifying the signature of the next before executing it, anchored in immutable hardware, so only authorised software runs.
Timeout Budget
Assigning a request an overall deadline at the edge and passing the remaining time down each hop, so no service works on something already out of time.
Unreachable Node
A component you cannot log into, restart or inspect, which removes every operational technique that assumes access to the running system.
A team proposes moving an API to edge functions to reduce latency for international users. What do you check before agreeing?
Where is the data? This is the question that settles most edge proposals. Compute at the edge that calls back to a single region database has moved the compute
A team proposes moving personalisation to edge functions to cut latency. When does that work and when does it backfire?
The principle that decides it The edge is near the user and far from your data. Edge compute pays off for work that needs the request but not your state . The m
A team wants to build a new internal API on serverless functions. It will serve steady traffic of about 200 requests per second during business hours. What do you advise?
What the interviewer is testing Whether you can apply the serverless trade off to a specific workload rather than treating it as a default good or a default bad
Architecture decisions in your organisation are either ignored or bottlenecked in a review board. Design something better.
Why both failure modes have the same cause A review board is a synchronous, low bandwidth, high latency channel: teams wait, decisions are made by people distan
Edge Functions
Short-lived compute at the CDN, its runtime limits, and what must stay at origin.
Edge Compute Topologies
Regional, metro, on-premises and on-device, and what each tier is genuinely for.
Edge Computing
Moving compute towards the user, and what cannot follow it.
Edge Data Consistency
Replicated read state at hundreds of locations, and writes that still go to one.
Edge Rendering
Running the render close to the user, and the personalisation and cache trade it implies.
Edge Security & Attestation
Secure boot, hardware roots of trust, and proving what is running on a device.
Edge, Mobile & IoT
General material on architecture beyond the data centre boundary.
Fitness Functions
Automated checks that an architectural characteristic still holds.
CRDTs
Data types that converge without coordination, and the semantics you must accept.
Compute Models
Instances, containers and functions, and what each is priced and shaped for.
Constrained Protocols
MQTT, CoAP and their kin, chosen for power, packet size and intermittent links.
Content Delivery Networks
Edge caching, origin offload, spike absorption and dynamic content.
Device Identity
Identifying a thing rather than a person, and rotating a credential you cannot type.
Device Provisioning
Getting identity and configuration onto hardware at manufacture or first boot.
Device Telemetry at Scale
Deciding what a device sends, how often, and what is aggregated before it leaves.
Digital Twin
A server-side model of a physical thing's reported and desired state.
Fleet Management
Inventory, health, configuration and grouping across devices you will never see.
IoT Ingest Architecture
Millions of small, unreliable, frequently duplicated messages arriving continuously.
Mobile App Architecture
Layering, navigation, background execution, and the platform rules you do not set.
Mobile Release Strategy
Store review, staged rollout, and supporting versions you can never force off.
OTA Updates
Updating firmware over a flaky link, with rollback, and without bricking the device.
Offline-First
Treating connectivity as an optimisation, with a local store as the source of truth.
Operating Models
How delivery, platform and governance functions fit together.
Physical-World Failure Modes
Power loss, tampering, clock drift, thermal limits, and a truck through the fibre.
Push & Background Work
Delivery that is best-effort, and an operating system that will kill your process.
Sync & Conflict Resolution
Two devices that both changed the same record while neither could see the other.
Synthetic Data
Generating data with the shape and edge cases of the real thing, and where it misleads.