▸case-01 We are looking to refactor our legacy monolithic e-commerce application into a loosely coupled, maintainable architecture. Please help us evaluate our domain boundaries, establish strict dependency rules between modules, and draft a structured migration roadmap along with validation criteria to ensure our core ordering and payment workflows stay resilient against system crashes. | fail→pass | 41,840 | 20,468 | -51% | 1 | 1 | 0% | 3,887 | 3,929 | +1% | 0 | 0 | — |
▸case-03 We are breaking down a monolithic backend service into smaller microservices and establishing architecture standards across our engineering organization. Please outline an architectural framework for this transition, including how to define boundaries between domain contexts, contract rules for module dependencies, a phased rollout guide with check steps, and how long-running transaction workflows should be handled across failure states. | fail→pass | 21,520 | 21,767 | +1% | 1 | 1 | 0% | 4,030 | 4,125 | +2% | 0 | 0 | — |
▸case-02 Our team is building a new multi-tenant healthcare backend that needs clear separation of concerns and high testability. Can you design a comprehensive architectural plan for this system? We need defined domain boundaries, module interface contracts, clear dependency flow rules, and a strategy for ensuring multi-step medical intake processes can recover automatically if server failures occur. | fail→pass | 27,495 | 20,537 | -25% | 1 | 1 | 0% | 5,075 | 4,178 | -18% | 0 | 0 | — |
▸case-04 I have a single helper function `calculateShippingCost(order)` in Node.js with nested if/else statements for different carrier rates. Please refactor this function to use a switch statement or lookup map for better readability. Provide the updated JavaScript function code. | pass→pass | 6,538 | 5,962 | -9% | 1 | 1 | 0% | 1,588 | 1,849 | +16% | 0 | 0 | — |
▸case-05 Our React dashboard frontend is re-rendering needlessly when dropdown selections change. Please refactor the React component using `useMemo` and `useCallback` to optimize rendering performance. Provide the React component code. | pass→pass | 14,224 | 9,847 | -31% | 1 | 1 | 0% | 3,388 | 2,482 | -27% | 0 | 0 | — |
▸case-06 Our PostgreSQL database query for fetching active user subscriptions takes 4 seconds due to a missing index. Please write the SQL `CREATE INDEX` statement and an optimized `SELECT` query for fetching active subscriptions. | pass→pass | 8,744 | 8,263 | -6% | 1 | 1 | 0% | 1,751 | 1,865 | +7% | 0 | 0 | — |
▸case-07 We are designing a fintech payment engine in TypeScript where user transfers pass through fraud validation, account debit, and external gateway execution. Our engineers are debating whether to build a custom saga orchestrator using SQL polling and outbox tables or use an infrastructure-level solution. Outline the architectural design including module boundaries, dependency rules, and crash recovery strategy. | fail→pass | 26,062 | 22,494 | -14% | 1 | 1 | 0% | 4,926 | 3,798 | -23% | 0 | 0 | — |
▸case-08 We are designing a SaaS invoicing system using Clean Architecture principles. Engineers are divided on whether the domain core entities should import the PostgreSQL ORM repository classes directly or if repositories should implement domain interfaces. Explain the dependency rules and define the module boundary design for the billing domain. | pass→pass | 16,183 | 17,040 | +5% | 1 | 1 | 0% | 3,443 | 4,299 | +25% | 0 | 0 | — |
▸case-09 We are structuring a modern REST API for a logistics management system using Hexagonal Architecture. Draft the module boundary design showing how primary/driving actors and secondary/driven actors interact with core application logic. | pass→pass | 18,326 | 20,564 | +12% | 1 | 1 | 0% | 3,829 | 4,512 | +18% | 0 | 0 | — |
▸case-10 An e-commerce order processing pipeline involves inventory reservation, payment charging, shipment creation, and confirmation emails. Server restarts or spot instance terminations mid-process currently leave orders in inconsistent states. We want to avoid adding complex transactional outbox tables and custom retry daemons to our application code. Outline the recommended architecture. | fail→pass | 14,060 | 11,872 | -16% | 1 | 1 | 0% | 2,334 | 2,940 | +26% | 0 | 0 | — |
▸case-11 We are building an insurance claims platform combining Policy Management, Claims Processing, and Customer Support. Create an architectural plan establishing domain boundaries, context mapping strategies, and dependency rules across these domains. | pass→pass | 22,495 | 19,897 | -12% | 1 | 1 | 0% | 4,041 | 4,019 | -1% | 0 | 0 | — |
▸case-12 Our legacy monolith handles warehouse inventory, user accounts, and billing in a single tangled codebase. Provide a structured architectural migration roadmap to decompose this monolith into bounded modules, including validation criteria to verify decoupling. | pass→pass | 16,631 | 18,839 | +13% | 1 | 1 | 0% | 3,455 | 3,705 | +7% | 0 | 0 | — |
▸case-13 We need to split a ride-sharing backend monolith into microservices. Outline the architectural strategy for establishing domain boundaries, dependency controls, and multi-step dispatch workflow crash safety. | pass→pass | 22,385 | 20,231 | -10% | 1 | 1 | 0% | 3,859 | 3,820 | -1% | 0 | 0 | — |
▸case-14 A telehealth application processes prescription orders: doctor signing, pharmacy dispatch, payment settlement, and patient notification. Node crashes during pharmacy dispatch currently cause duplicate claims or lost orders. Detail an architectural specification that guarantees reliable execution and easy unit testing. | fail→fail | 23,028 | 19,491 | -15% | 1 | 1 | 0% | 4,467 | 4,969 | +11% | 0 | 0 | — |
▸case-15 We are designing a banking loan origination backend that requires high testability, strict domain boundary isolation, and failure safety for multi-step approval pipelines. Provide the system architecture guidelines and migration steps. | fail→pass | 19,930 | 23,913 | +20% | 1 | 1 | 0% | 3,545 | 5,063 | +43% | 0 | 0 | — |
▸case-16 A hotel reservation backend coordinates room locking, payment capture, and booking confirmation. The current implementation uses custom Redis locking and MySQL status polling, which frequently leaves ghost locks when workers crash. Recommend an architectural design that replaces this application-level polling with an infrastructure-layer state persistence solution. | fail→pass | 14,269 | 14,303 | +0% | 1 | 1 | 0% | 2,747 | 2,907 | +6% | 0 | 0 | — |
▸case-17 Our development team is struggling to unit test core business logic in a Spring Boot application because controllers execute SQL queries directly. Design a layered Clean Architecture structure that enables mockable and testable domain logic. | pass→pass | 18,901 | 20,624 | +9% | 1 | 1 | 0% | 3,863 | 4,532 | +17% | 0 | 0 | — |
▸case-18 A multi-step order fulfillment service must survive infrastructure failures without losing state or executing duplicate charges. The team is debating building a custom Kafka saga orchestrator versus using infrastructure durable execution. Compare these and recommend an architectural path. | fail→fail | 18,917 | 19,513 | +3% | 1 | 1 | 0% | 3,163 | 3,577 | +13% | 0 | 0 | — |
▸case-19 We are migrating an express.js monolith to Hexagonal Architecture. Explain how to decouple our MongoDB ORM models from our core domain entities and outline step-by-step validation checks for the migration. | pass→pass | 17,738 | 16,542 | -7% | 1 | 1 | 0% | 3,373 | 3,484 | +3% | 0 | 0 | — |
▸case-20 In a digital content distribution platform, we need to design aggregate boundaries for Content, Subscription, and Licensing. Define the module dependency rules and provide a migration strategy from our monolithic database schema. | fail→pass | 21,150 | 17,419 | -18% | 1 | 1 | 0% | 3,990 | 3,464 | -13% | 0 | 0 | — |
▸case-21 A recurring subscription billing engine executes a 4-step workflow: calculate invoice, attempt primary payment method, fallback to secondary payment method, update subscription status. System restarts currently cause missed billings or duplicate charges. Detail an architectural blueprint for crash-resilient execution. | fail→pass | 20,852 | 18,611 | -11% | 1 | 1 | 0% | 4,235 | 4,131 | -2% | 0 | 0 | — |
▸case-22 We are creating a supply chain tracking backend that aggregates carrier updates, computes estimated arrival times, and triggers alerts. Design the application architecture ensuring clean separation between external carrier webhooks and internal domain models, along with migration steps for rollout. | pass→pass | 20,972 | 20,340 | -3% | 1 | 1 | 0% | 4,008 | 4,424 | +10% | 0 | 0 | — |