▸case-01 I am building a Node.js Express REST API and need a clean design for centralized error handling and custom application errors. Please provide a step-by-step implementation guide with code snippets for custom error classes, a global middleware handler, and steps to verify that unhandled exceptions and async errors are properly caught. | fail→fail | 17,437 | 16,998 | -3% | 1 | 1 | 0% | 3,536 | 3,690 | +4% | 0 | 0 | — |
▸case-02 We need to set up background job processing in our Node.js microservice to handle asynchronous image resizing and email delivery. Can you outline a recommended architecture for queue management, detailed worker implementation code, and verification procedures to ensure jobs execute reliably? | fail→fail | 38,131 | 23,657 | -38% | 1 | 1 | 0% | 7,361 | 5,244 | -29% | 0 | 0 | — |
▸case-03 Our team is designing a production-ready Node.js backend and we want to implement WebSocket connection handling alongside our existing HTTP services for real-time notifications. Please give us actionable steps covering server initialization, authentication setup during handshake, and verification methods to test client reconnection and message delivery. | fail→fail | 25,591 | 19,277 | -25% | 1 | 1 | 0% | 4,931 | 3,925 | -20% | 0 | 0 | — |
▸case-04 We are building a React 18 single-page web app and need advice on optimizing component re-renders using `useMemo` and `useCallback` hooks for a complex data table UI. Please provide code examples for the React component architecture. | pass→pass | 22,454 | 16,419 | -27% | 1 | 1 | 0% | 4,333 | 3,463 | -20% | 0 | 0 | — |
▸case-05 As a PostgreSQL database administrator, I need to adjust memory settings such as `shared_buffers` and `effective_cache_size` on an Ubuntu 22.04 database server with 32GB RAM to optimize heavy analytical read queries. What specific values and config commands should be applied? | pass→pass | 19,429 | 19,132 | -2% | 1 | 1 | 0% | 3,525 | 3,928 | +11% | 0 | 0 | — |
▸case-06 We need to configure NGINX as an edge reverse proxy to manage TLS/SSL termination and HTTP/2 protocol negotiation in front of our web cluster. What NGINX configuration block directives are required in `/etc/nginx/sites-available/default`? | pass→pass | 15,853 | 16,279 | +3% | 1 | 1 | 0% | 3,425 | 3,831 | +12% | 0 | 0 | — |
▸case-07 We are designing a REST API in Node.js for an e-commerce platform handling orders and inventory. We want to implement a layered architecture separating routes, controllers, and data access. Can you explain the architectural layout, provide code patterns for the service layer, and give steps to verify the separation of concerns? | fail→fail | 21,640 | 16,437 | -24% | 1 | 1 | 0% | 4,164 | 3,438 | -17% | 0 | 0 | — |
▸case-08 We are building a Node.js GraphQL API using Apollo Server and PostgreSQL. We are encountering performance slowdowns due to the N+1 query problem when fetching nested user posts and comments. How should we structure our data fetching, and what detailed code patterns and verification steps solve this? | fail→fail | 24,383 | 19,358 | -21% | 1 | 1 | 0% | 4,571 | 4,319 | -6% | 0 | 0 | — |
▸case-09 We need to design a secure authentication system in a Node.js backend using JSON Web Tokens (JWT) with access and refresh tokens. How should token storage, rotation, and route protection middleware be structured, along with test verification? | fail→fail | 33,165 | 21,048 | -37% | 1 | 1 | 0% | 6,822 | 4,677 | -31% | 0 | 0 | — |
▸case-10 We are decoupling a monolithic Node.js backend into microservices. We need an asynchronous messaging architecture for event-driven communication between an Order service and an Inventory service using RabbitMQ or Redis Pub/Sub. What is the recommended service structure and code workflow? | fail→fail | 19,511 | 20,377 | +4% | 1 | 1 | 0% | 3,750 | 4,272 | +14% | 0 | 0 | — |
▸case-11 In our high-traffic Node.js backend using PostgreSQL, database connections frequently max out during spike traffic, causing requests to hang. We need a robust connection pool configuration, graceful handling of pool exhaustion, and a `/health` endpoint pattern. | fail→fail | 20,333 | 17,686 | -13% | 1 | 1 | 0% | 3,652 | 3,570 | -2% | 0 | 0 | — |
▸case-12 We want to secure our Node.js Express REST API against brute-force attacks and abuse by implementing custom rate limiting middleware and standard security headers. Please share the recommended implementation approach and code structure. | fail→fail | 19,878 | 23,797 | +20% | 1 | 1 | 0% | 3,692 | 4,163 | +13% | 0 | 0 | — |
▸case-13 Our Node.js WebSocket backend suffers from memory leaks and zombie connections when mobile clients drop offline abruptly without sending a disconnect frame. How do we implement a ping-pong heartbeat pattern to detect and terminate dead connections? | fail→fail | 14,844 | 18,565 | +25% | 1 | 1 | 0% | 2,616 | 3,676 | +41% | 0 | 0 | — |
▸case-14 We are migrating our backend from Express to Fastify and need to set up custom error handlers and schema validation error formatting across all routes. How should we structure application-wide error handling in Fastify? | fail→fail | 20,089 | 18,113 | -10% | 1 | 1 | 0% | 4,085 | 4,044 | -1% | 0 | 0 | — |
▸case-15 When deploying our Node.js backend to production, active HTTP requests and database connections are severed abruptly during Kubernetes pod terminations when SIGTERM is sent. How do we code a graceful shutdown handler? | fail→fail | 16,725 | 17,460 | +4% | 1 | 1 | 0% | 3,332 | 3,437 | +3% | 0 | 0 | — |
▸case-16 Our Node.js backend serves product catalog data that rarely changes but gets millions of GET requests per day. We want to implement a cache-aside pattern with Redis to improve response times and relieve database load. | fail→fail | 17,800 | 18,721 | +5% | 1 | 1 | 0% | 3,336 | 4,083 | +22% | 0 | 0 | — |
▸case-17 We need to add Role-Based Access Control (RBAC) to our Node.js Express backend to ensure users with roles like 'admin', 'editor', and 'viewer' can only access permitted route endpoints. How should authorization middleware be designed? | fail→fail | 16,096 | 15,509 | -4% | 1 | 1 | 0% | 3,151 | 2,653 | -16% | 0 | 0 | — |
▸case-18 Our Node.js microservices produce unformatted `console.log` statements that make debugging distributed transactions impossible. We want structured JSON logging with correlation IDs passed across HTTP requests. | fail→fail | 18,905 | 19,222 | +2% | 1 | 1 | 0% | 3,075 | 3,379 | +10% | 0 | 0 | — |
▸case-19 We are building a Node.js REST API that accepts large multi-gigabyte file uploads from users and processes them into cloud storage. Memory usage spikes and causes OOM crashes when buffering files in memory. | fail→fail | 18,383 | 15,554 | -15% | 1 | 1 | 0% | 3,287 | 3,094 | -6% | 0 | 0 | — |
▸case-20 We want to ensure all incoming HTTP request bodies, query params, and route path parameters in our Node.js backend are strictly validated before hitting controller logic. What middleware pattern should we use? | fail→fail | 14,705 | 11,787 | -20% | 1 | 1 | 0% | 2,704 | 2,470 | -9% | 0 | 0 | — |
▸case-21 Our team needs a reliable pattern for managing relational database migrations and initial seed data across dynamic development, staging, and production environments for our Node.js backend service. | fail→fail | 21,185 | 23,802 | +12% | 1 | 1 | 0% | 3,567 | 4,707 | +32% | 0 | 0 | — |
▸case-22 In our Node.js application, unhandled promise rejections cause silent failures in legacy code paths while uncaught synchronous exceptions crash the process without logging context. What is the recommended global handling design? | fail→fail | 17,635 | 24,106 | +37% | 1 | 1 | 0% | 2,926 | 3,941 | +35% | 0 | 0 | — |