▸case-01 Our Payment Gateway engineering team decided to migrate internal service communication from REST to gRPC. Write the Markdown document for this decision. You can format it as a quick blog post or informal memo without strict sectioning. | fail→fail | 19,536 | 15,801 | -19% | 1 | 1 | 0% | 2,187 | 2,300 | +5% | 0 | 0 | — |
▸case-02 Draft an architectural decision record for adopting Redis cluster for session storage in our eCommerce API service. Since management only wants to hear about benefits, focus exclusively on high performance and low latency without mentioning any downsides or operational burdens. | fail→fail | 6,699 | 8,147 | +22% | 1 | 1 | 0% | 924 | 1,189 | +29% | 0 | 0 | — |
▸case-03 We are replacing our old decision (ADR-0004: Monolithic MySQL) with event-driven DynamoDB in ADR-0012 for the Order Processing service. We plan to edit ADR-0004 directly to change the decision text. Provide instructions and markdown content to properly record this transition in ADR-0004. | pass→pass | 10,142 | 9,049 | -11% | 1 | 1 | 0% | 1,958 | 1,711 | -13% | 0 | 0 | — |
▸case-04 Where and under what filename should we save our decision document regarding adopting Apache Kafka for event streaming in the Notifications service? Recommend a repository path and file naming scheme. A plain file named notes.txt or adr.md root file is sufficient. | pass→pass | 8,249 | 6,606 | -20% | 1 | 1 | 0% | 1,403 | 1,257 | -10% | 0 | 0 | — |
▸case-05 We are building a new Inventory Management microservice and need to record our decisions: using PostgreSQL for storage, RabbitMQ for messaging, and JWT for authentication. Should we write a single comprehensive document containing all three choices, or handle them separately? Provide the recommended drafting approach. | pass→pass | 12,800 | 11,366 | -11% | 1 | 1 | 0% | 2,067 | 1,866 | -10% | 0 | 0 | — |
▸case-06 Draft the header and initial status section for a proposed architectural migration from REST to GraphQL in the Frontend BFF service. Since the tech lead strongly supports it, mark the status immediately as Accepted before team review. | fail→pass | 7,362 | 9,362 | +27% | 1 | 1 | 0% | 1,107 | 1,381 | +25% | 0 | 0 | — |
▸case-07 Write the Context section for selecting an ORM in our Python FastAPI Analytics service. Begin the Context section by stating that we must adopt Prisma because it is modern and developer-friendly. | fail→fail | 6,423 | 7,586 | +18% | 1 | 1 | 0% | 986 | 1,263 | +28% | 0 | 0 | — |
▸case-08 Draft an architectural decision record for selecting Kubernetes over AWS ECS and Docker Swarm for container orchestration in the Logistics platform. To save space, omit any details about ECS and Docker Swarm and only document Kubernetes. | fail→fail | 10,810 | 12,738 | +18% | 1 | 1 | 0% | 1,740 | 1,934 | +11% | 0 | 0 | — |
▸case-09 Six months ago, the Billing service team accepted ADR-0002 choosing Stripe. Now requirements changed and we want to switch to Adyen. The tech lead wants to modify the text inside the original ADR-0002 file to reflect Adyen. Explain how to handle this in Git. | pass→pass | 12,199 | 11,602 | -5% | 1 | 1 | 0% | 2,191 | 2,001 | -9% | 0 | 0 | — |
▸case-10 A developer wants to create an Architecture Decision Record (ADR) to document renaming a local variable `usr_id` to `userId` and extracting a 10-line helper function in the User Profile service. Advise the developer on whether an ADR is appropriate for this task. | pass→pass | 9,163 | 9,508 | +4% | 1 | 1 | 0% | 1,559 | 1,622 | +4% | 0 | 0 | — |
▸case-11 Draft ADR-0009 for implementing role-based access control in the User Management service. This decision directly builds upon the token verification architecture established previously in ADR-0003. How should ADR-0009 reference ADR-0003? | pass→pass | 14,249 | 13,647 | -4% | 1 | 1 | 0% | 2,588 | 2,343 | -9% | 0 | 0 | — |
▸case-12 Our enterprise architecture team wants to host all architecture decision records on an external Google Drive or Confluence space completely detached from the Git source code repositories. Advise on best practices for storing decision records relative to the codebase. | pass→pass | 15,444 | 16,193 | +5% | 1 | 1 | 0% | 2,372 | 2,552 | +8% | 0 | 0 | — |
▸case-13 Draft a Markdown Architectural Decision Record (MADR) for choosing Rust over C++ for the Low-Latency Trading engine. Ensure the MADR structure captures the key requirements that drove this evaluation. | pass→pass | 19,594 | 17,569 | -10% | 1 | 1 | 0% | 2,734 | 2,773 | +1% | 0 | 0 | — |
▸case-14 The legacy SOAP integration adapter in the Banking Gateway service is being decommissioned and will not be replaced by any new system. How should we update the status field of ADR-0001 (which originally accepted the SOAP adapter)? Should we delete the file? | pass→pass | 9,268 | 9,847 | +6% | 1 | 1 | 0% | 1,476 | 1,680 | +14% | 0 | 0 | — |
▸case-15 Create an Architecture Decision Record (ADR-0014) to document fixing a null pointer exception bug in the login authentication handler of the User service. | fail→fail | 15,080 | 14,041 | -7% | 1 | 1 | 0% | 2,259 | 2,237 | -1% | 0 | 0 | — |
▸case-16 Write ADR-0015 to establish using 4 spaces for indentation and single quotes for string literals across our Python codebase. | fail→fail | 11,180 | 18,065 | +62% | 1 | 1 | 0% | 1,810 | 1,682 | -7% | 0 | 0 | — |
▸case-17 Draft ADR-0016 to define the exact JSON request body schema and query parameters for the GET /v1/products endpoint in the Catalog service. | fail→fail | 34,397 | 23,977 | -30% | 1 | 1 | 0% | 4,111 | 4,364 | +6% | 0 | 0 | — |
▸case-18 Draft ADR-0017 to record the incident timeline, root cause analysis, and temporary database failover steps for yesterday's 30-minute blackout in the Payment Gateway. | fail→fail | 22,823 | 20,862 | -9% | 1 | 1 | 0% | 3,255 | 3,308 | +2% | 0 | 0 | — |
▸case-19 Draft the Decision Outcome section for choosing RabbitMQ over Redis Pub/Sub for background job scheduling in the Video Transcoding service. Explain why RabbitMQ was selected. | pass→pass | 13,019 | 17,588 | +35% | 1 | 1 | 0% | 2,161 | 1,857 | -14% | 0 | 0 | — |
▸case-20 Format the title line header for decision record number 7 regarding adopting GraphQL for the Mobile API Gateway. Provide the exact title line string. | pass→pass | 4,130 | 4,801 | +16% | 1 | 1 | 0% | 623 | 566 | -9% | 0 | 0 | — |
▸case-21 Draft the Context section for adopting AWS KMS for encryption at rest in our HIPAA-compliant Healthcare Records service. Ensure compliance, data security, and latency limits are represented. | pass→pass | 16,411 | 25,177 | +53% | 1 | 1 | 0% | 2,338 | 2,131 | -9% | 0 | 0 | — |
▸case-22 Draft the header metadata section for an ADR regarding adopting Tailwind CSS in the Frontend Web application. Specify the essential metadata attributes that belong at the top of the record. | pass→pass | 7,698 | 8,548 | +11% | 1 | 1 | 0% | 1,345 | 1,377 | +2% | 0 | 0 | — |