Search the practice set
275 questions, 991 terms and 600 topics in 30 areas.
27 results for “Cross-Border Transfer”
Transfer Mechanism
The specific legal instrument permitting personal data to leave a jurisdiction, which must exist per flow and which architecture must make identifiable.
Cross-Zone Data Transfer
Charges incurred when data moves between availability zones within a region — invisible on architecture diagrams and a recurring surprise on cloud bills.
Cross-Zone Load Balancing
Whether a load balancer node distributes traffic to targets in all zones or only its own — a setting that affects both balance and data transfer cost.
Cross-Cutting Concern
A responsibility that legitimately appears throughout a system rather than in one module, such as logging, authorisation, tracing or transaction management.
Cross-Functional Requirement
A quality the system must exhibit across its features rather than a behaviour it must perform, so named because it cuts across all functionality.
Cross-Service Debugging
Investigating a failure that spans multiple services by moving between traces, logs, metrics and profiles along a single correlated request.
API Gateway
A single entry point in front of a set of services that handles authentication, rate limiting, routing and protocol translation.
Agent Handoff
The transfer of a task and its context from one specialised agent to another, and the point at which multi-agent systems most often lose information.
BGP
The protocol by which autonomous systems advertise which address ranges they can reach, determining how traffic finds any destination on the internet.
Egress Cost
The charge for moving data out of a cloud provider or across its zones and regions — usually the least-anticipated line on a cloud bill.
Egress Path Analysis
Tracing where data physically moves in an architecture, because transfer charges follow paths that appear nowhere on the diagram.
End-to-End Test Cost Curve
How the cost of a broad end-to-end suite grows with its size while its marginal value falls, and where the two cross.
Gateway Offloading
Moving cross-cutting concerns — TLS termination, authentication, rate limiting, compression, logging — from every service into the gateway.
Log Schema Consistency
Enforcing the same field names, types and semantics for structured log records across every service, so cross-service queries are possible.
Pattern Recognition
Recognising that a novel-looking problem is an instance of one you have seen before, and knowing which parts of the previous solution transfer.
Payload Compression Trade-off
The exchange of CPU time for reduced transfer time, which is favourable on constrained networks and harmful on fast local ones.
Sidecar
Deploying a helper process alongside the main application in the same unit, to supply cross-cutting behaviour without changing the application.
Value Stream
The end-to-end sequence of activities that delivers a result to a customer, viewed across whatever departments and systems it happens to cross.
Cross-Border Transfer
The legal mechanism that permits data to leave, and the architecture that respects it.
Network & Egress Costs
Cross-zone and cross-region transfer that appears on no diagram.
Agent Architectures
Loops, planning, memory and the boundaries an agent must not cross.
Managed Services
Which operational responsibilities actually transfer, and which do not.
Reranking
Cross-encoders improving precision more than a bigger embedding model.
Sidecar & Ambassador
Cross-cutting behaviour in a co-deployed process.
Streaming Cost
Always-on compute, retention and cross-zone traffic as the three bills that surprise.