Loading
Pick a focused question that fits your time, stack, and interview goal.
39 results across 1 active filter
Page 1 of 2
Builds a FastAPI POST boundary with separate input/output models, forbidden extra fields, domain mapping, and a 201 response.
Uses SQLAlchemy version counters and an HTTP precondition to reject stale writes without silently overwriting newer state.
Explains acquisition and cleanup around `yield`, including request and function scopes, streaming, and exception-safe ownership.
Traces a request from the ASGI server through middleware, routing, dependencies, validation, handler execution, and response completion.
Explains FastAPI parameter-source inference and when explicit markers make an HTTP contract clearer.
Explains dependency graphs, sub-dependencies, request-local caching, failures, and deliberate cache bypass.
Uses separate Pydantic input and output models to prevent mass assignment and accidental data disclosure.
Explains how input conversion, strict validation, and extra-field policies change what an API accepts and preserves.
Locates pre-handler failures across proxies, routing, parsing, validation, dependencies, and middleware using structured evidence.
Models partial updates without confusing omitted fields, explicit nulls, defaults, or unauthorized changes.
Controls operation identities, request and response schemas, error documentation, and compatibility checks without hand-maintaining a second contract.
Streams bounded chunks with explicit resource lifetime, cancellation, late-failure, and proxy behavior.
Overrides FastAPI boundaries for focused tests and restores the global override mapping reliably.
Handles multipart uploads with bounded size, untrusted metadata, content inspection, controlled storage, scanning, and cleanup.
Keeps FastAPI dependency resolution at transport and composition boundaries while application services use explicit dependencies.
Trusts proxy-derived scheme, host, and client data only from known hops and configures externally visible paths correctly.
Coordinates readiness, signals, request drain, lifespan cleanup, and a bounded termination deadline.
Uses FastAPI lifespan to create and close process-owned resources around request serving.
Uses Pydantic models as explicit transport contracts without making them persistence or domain models automatically.
Treats Python web workers as measured processes with separate memory, lifecycle, and failure boundaries.
Separates process survival, traffic readiness, and slow initialization without turning shared dependency failure into a restart storm.
Maps validation, HTTP, domain, and unexpected failures into a stable client contract while preserving diagnostics.
Uses FastAPI Security dependencies to combine declared scopes with current application authorization.
Uses routers as feature-oriented HTTP modules while keeping application logic, composition, and contract ownership clear.