Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
60 results for “Edge Compute Topologies”
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.
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.
Compute Isolation Boundary
The line across which one domain's analytical workload cannot affect another's performance, cost attribution or access.
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.
Team Topologies
A model of four team types and three interaction modes used to design an organisation deliberately for a target architecture and flow of change.
Admission Control
Deciding at the edge whether to accept a request at all, based on current capacity, before any work is done on it.
Burstable Instance
An instance that provides a low baseline CPU allocation and accrues credits while idle, spendable for short periods of full performance.
Cloud Pricing Models
The purchase options for cloud compute — on-demand, committed use, and spot — which differ by up to 90% for identical hardware.
Cognitive Load
The total amount a team must hold in its head to work effectively, and a real constraint on how many services or domains one team can own.
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.
ETL vs ELT
Whether data is transformed before loading into the target or after it, which decides where the compute happens and how much raw history you keep.
Egress Pricing
The asymmetric charging model in which data entering a cloud is free and data leaving is billed, shaping architecture more than compute pricing does.
Enabling Team
A team whose output is other teams' increased capability, working alongside them temporarily and deliberately removing itself.
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.
Instance Family
A group of instance types sharing a resource profile — general purpose, compute optimised, memory optimised, storage optimised, accelerated — chosen by which resource the workload…
Instance Family Selection
Matching a workload's resource profile to a machine type designed for it, which is frequently a larger saving than reducing size.
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.
Serverless
A model where the provider allocates and scales compute per request, and you are billed for execution rather than for provisioned capacity.
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
Your observability bill is now 40% of your compute bill. Leadership wants it cut in half without going blind. What do you cut?
What the interviewer is testing Whether you understand what each telemetry type is for , so you can cut the redundant parts rather than cutting uniformly — whic
A fleet of 200 instances averages 15% CPU and 85% memory. Finance wants a 40% cost reduction. What do you do?
The diagnosis The instance family is wrong. 15% CPU and 85% memory means the workload is memory bound running on general purpose or compute optimised instances,
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 Functions
Short-lived compute at the CDN, its runtime limits, and what must stay at origin.
Compute Models
Instances, containers and functions, and what each is priced and shaped for.
Compute Optimisation
Instance families, utilisation, and architecture that wastes less.
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.
Platform Team Topologies
Stream-aligned, enabling, complicated-subsystem and platform teams, and their interactions.
Team Topologies
Stream-aligned, platform, enabling and complicated-subsystem teams.
CRDTs
Data types that converge without coordination, and the semantics you must accept.
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.
Data Platform Tenancy
Multiple domains on shared storage and compute, with separable access and cost.
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.
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.
Streaming Cost
Always-on compute, retention and cross-zone traffic as the three bills that surprise.
Sync & Conflict Resolution
Two devices that both changed the same record while neither could see the other.