▸case-01 We are building a multi-channel retail system that needs to handle high-volume flash sales without crashing during checkout spikes. Please act as a system architect and design the backend infrastructure for processing orders and managing inventory. I need a comprehensive proposal that details the service boundaries, API contracts, asynchronous event flow, fault isolation mechanisms, caching layout, and operational monitoring strategy, along with a list of key technical trade-offs. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-19 Updating our core API service currently requires taking the backend offline for 20 minutes. Propose an operational deployment strategy to achieve seamless releases without user downtime. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-13 We are designing a multi-tenant enterprise system where backend services must verify user identity tokens and secure internal service calls without sharing database credentials. Design the security architecture. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-06 Our UI design team needs help building a responsive React dashboard layout with Tailwind CSS grid classes, modal dialogue accessibility attributes, and component state hooks. How should we build this web interface? | fail→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-16 Malformed event payloads intermittently cause our message processing workers to throw unhandled parsing exceptions and crash continually. Architect an error handling strategy for asynchronous queues. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-03 We are planning to refactor an old monolithic SaaS platform into a modern distributed system to improve scale and deployment speed. Please help us architect this migration. We need a detailed plan covering the service decomposition strategy, API gateway and Backend-for-Frontend design, inter-service API specifications, data synchronization and communication patterns, resilience patterns for legacy rollbacks, and an observability plan for cross-service requests. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-25 Backend service updates frequently break third-party client integrations because developers remove fields from JSON responses without knowing downstream dependencies. Architect a testing pipeline mechanism to prevent breaking API changes. | pass→pass | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-04 I have a Python script that throws a KeyError when parsing incoming JSON payloads in my route handler. Here is the script snippet: def handle_data(payload): return payload['user_id']. Please fix this code snippet bug. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-22 Generating PDF reports takes 45 seconds per request. Web clients hit gateway timeouts when calling the synchronous export API. Architect a non-blocking execution mechanism with progress tracking. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-15 Our activity log service queries billions of rows. High offset queries like OFFSET 500000 cause severe database timeouts. Design an API pagination contract that scales efficiently. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-08 Our payment gateway integration fails intermittently with 503 errors during traffic spikes. Developers plan to loop retries continuously in a tight synchronous while loop. Architect an integration strategy to handle downstream payment failures safely. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-23 Our IoT telemetry platform receives 100,000 write events per second while executives run heavy analytical reporting queries on the same relational database tables. Architect a design pattern to decouple write ingestion from reporting reads. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-12 We are designing a collaborative whiteboard API. Developers are debating between polling REST endpoints every 500ms or using an event push pattern over an open connection. Structure the real-time API communication model. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-24 Debugging errors across our 15 microservices is difficult because logs across services cannot be linked to the original user request. Architect a cross-service tracking strategy. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-07 We are architecting an e-commerce platform with Order Management and Payment services. Please define the microservice boundaries and API contracts. In addition, write the exact PostgreSQL CREATE TABLE DDL scripts for order items. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-14 Mobile app users on spotty connections often hit timeouts on POST /v1/transfers and tap Submit multiple times, triggering duplicate money transfers. Architect an API control mechanism to eliminate duplicate financial operations. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-05 We are building a logistics database in PostgreSQL. Write the full third normal form SQL CREATE TABLE statements, foreign key constraints, and B-tree indexing scripts for our shipment tracking tables. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-02 Our startup is constructing a real-time document editing app that requires instant messaging and notifications across web and mobile clients. Could you structure the backend service framework for us? Please outline the service division and responsibilities, provide the API contract specifications, explain the real-time push mechanism alongside back-end queuing, specify how to handle dropped connections or downstream service failures, and detail the distributed logging and tracing framework. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-20 Our e-commerce product catalog receives 500 times more reads than writes. High traffic spikes cause database CPU starvation. Architect a caching architecture specifying cache pattern and invalidation model. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-10 Our travel platform requires coordinating flight booking, hotel reservation, and payment across three independent backend services. Avoid two-phase commits while maintaining eventual consistency if a step fails during checkout. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-18 Our single backend REST API serves both smartwatches with strict network constraints and desktop web browsers requiring complex data views. Smartwatches are slowed down by bloated payloads. Design a tailored backend interface architecture. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-11 Scraping bots are overloading our backend servers. Engineers want to add custom IP-checking code inside every individual service endpoint. Architect a centralized traffic control solution. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-09 We are building an outbound webhook delivery system for enterprise clients who report missing events and duplicate deliveries. Architect a robust webhook dispatch mechanism addressing security and delivery guarantees. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-17 We have a monolithic application. Management wants to shut it down completely and re-write every feature in microservices during a single weekend. Recommend an architectural strategy that minimizes deployment risk. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |
▸case-21 In our auto-scaling cloud cluster, backend service containers frequently start and stop with dynamic IP addresses. Hardcoding IP addresses in static config files causes service connection failures. Design an address resolution architecture. | fail→fail | — | — | — | — | — | — | — | — | — | — | — | — |