Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
391 results across 1 active filter
Page 8 of 17
Reuses bounded redis-py pools for the application lifetime and closes async resources deliberately.
Coordinates readiness, signals, request drain, lifespan cleanup, and a bounded termination deadline.
Uses Resource Server and JwtDecoder to validate signature, issuer, audience, time, algorithms, key rotation, and authority mapping.
Separates stale checkout protection, connection aging, pool waits, statement timeouts, and uncertain transactions.
Treats cancellation as cooperative control flow with reliable resource cleanup and propagation.
Makes duplicate-key behavior explicit through validation, merge policies, grouping, and deterministic map selection.
Chooses stable entity equality across transient, managed, detached, and proxied instances without breaking hash collections.
Uses FastAPI lifespan to create and close process-owned resources around request serving.
Treats interruption as a cooperative request, preserves interrupt status, defines cleanup, and separates cancellation signals from guaranteed task termination.
Separates restart-worthy process failure from traffic readiness and composes Spring Boot health groups around those meanings.
Places the application class above owned components, uses capability-oriented packages, and keeps scanning and imports deliberate.
Stores salted adaptive password hashes, supports algorithm migration, and separates password verification from encryption.
Uses Pydantic models as explicit transport contracts without making them persistence or domain models automatically.
Keeps Celery messages small, safe to deserialize, and compatible across rolling deployments.
Aligns pytest-asyncio discovery, loop lifetime, and async fixture ownership without custom loop competition.
Defines one explicit SQLAlchemy session and transaction owner for each request, job, thread, or async task.
Builds outbound resilience from deadlines and operation safety, then adds bounded retry, circuit, and concurrency controls with telemetry.
Designs backpressure, worker ownership, completion tracking, failure, and shutdown around asyncio queues.
Treats Python web workers as measured processes with separate memory, lifecycle, and failure boundaries.
Builds an immutable Java type through valid construction, final state, defensive copying, controlled exposure, and safe sharing.
Separates process survival, traffic readiness, and slow initialization without turning shared dependency failure into a restart storm.
Combines selective Celery retries with bounded backoff, idempotent effects, and a terminal failure path.
Finds repeated relationship queries and fixes the data shape without introducing a larger query problem.
Connects one slow Python request to generated SQL, representative parameters, database plans, and measured validation.