▸case-01 We are building an e-commerce platform where the Order context needs to talk to a legacy Mainframe Accounting system. Team members suggest letting the Order context directly parse and use the Mainframe's COBOL data structures across all internal Order service classes to avoid mapping overhead. Map out the integration between Order and Mainframe Accounting, specifying relationship patterns, ownership, translation strategies, and failure risks. | pass→pass | 23,722 | 23,796 | +0% | 1 | 1 | 0% | 3,670 | 3,674 | +0% | 0 | 0 | — |
▸case-02 Our Inventory service needs stock updates from a third-party Supplier API that changes its payload formats frequently without notice. Developers want to write Inventory database queries directly against the vendor's webhook payloads. Provide a context mapping plan that addresses boundary translation, contract ownership, and risk mitigations. | pass→pass | 21,123 | 17,463 | -17% | 1 | 1 | 0% | 3,336 | 2,825 | -15% | 0 | 0 | — |
▸case-07 We are integrating a modern Claims Processing service with an external legacy Underwriting context. The legacy system cannot be modified under any circumstances. A developer suggested putting translation logic inside the legacy system. Create a context mapping plan covering relationship mapping, translation rules, contract ownership, and failure behavior. | pass→pass | 23,130 | 15,644 | -32% | 1 | 1 | 0% | 3,544 | 2,692 | -24% | 0 | 0 | — |
▸case-03 We have a Fraud Detection service that requires real-time transaction data from the Payments service. The Payments team agrees to modify their schema whenever Fraud needs a new field, and both teams share a common database library containing shared domain entities. Create a context mapping output specifying relationship choices, contract ownership, translation rules, and coupling risks. | fail→fail | 16,188 | 18,663 | +15% | 1 | 1 | 0% | 2,498 | 3,166 | +27% | 0 | 0 | — |
▸case-04 The Marketing context needs user behavior analytics from the User Account context. The User Account team is overloaded and refuses to build custom endpoints for Marketing, telling them to 'take the API as-is or leave it'. Outline the integration mapping including context relationship patterns, dependency direction, contract ownership, and translation decisions. | fail→fail | 18,336 | 15,180 | -17% | 1 | 1 | 0% | 2,877 | 2,627 | -9% | 0 | 0 | — |
▸case-05 Two core contexts, Checkout and Payment Processing, are developed by closely aligned teams in the same business unit that co-design feature releases together. They want to know whether to enforce a strict one-way customer-supplier relationship or adopt a cooperative approach. Provide a context mapping document covering context pairs, relationship patterns, contract ownership, translation rules, and coupling risks. | pass→pass | 37,700 | 25,527 | -32% | 1 | 1 | 0% | 5,997 | 4,225 | -30% | 0 | 0 | — |
▸case-06 Our enterprise system consists of a Core Logistics context and five separate consumer contexts (Reporting, Mobile App, Partner Portal, Warehouse, and Billing). Developers propose creating 5 custom tailored integration interfaces, one for each consumer. Provide a context map with relationship patterns, contract ownership, translation rules, and coupling mitigations. | pass→pass | 23,568 | 24,745 | +5% | 1 | 1 | 0% | 3,709 | 4,198 | +13% | 0 | 0 | — |
▸case-08 A company operates a Shipping context and an Order Fulfillment context where both teams operate independently with separate deployment pipelines. They want to share a single C# DLL containing all domain classes to ensure data structures match exactly. Provide a context mapping plan detailing integration patterns, ownership matrix, translation decisions, and risk mitigations. | pass→pass | 28,227 | 22,110 | -22% | 1 | 1 | 0% | 4,592 | 3,777 | -18% | 0 | 0 | — |
▸case-09 Our Recommendation Engine context needs product metadata from Catalog context. Catalog provides a rich GraphQL schema, but Recommendation Engine only cares about 3 attributes (ID, Category, Price). Developers want Recommendation Engine to store full Catalog schema objects in its database. Map out this context integration with patterns, contract ownership, translation decisions, and risk analysis. | pass→pass | 23,985 | 17,061 | -29% | 1 | 1 | 0% | 3,637 | 3,034 | -17% | 0 | 0 | — |
▸case-10 We are designing the boundaries between Patient Management, Billing, and Notifications in a healthcare platform. Patient Management triggers events when patient details update. Map out all context pairs, dependency directions, relationship patterns, contract ownership, translation mechanisms, and failure or fallback policies. | pass→pass | 28,330 | 23,769 | -16% | 1 | 1 | 0% | 4,654 | 4,154 | -11% | 0 | 0 | — |
▸case-11 A retail system integrates Warehouse Management and Online Storefront contexts. The Storefront team frequently breaks Warehouse integration because contract changes are done verbally with no formal versioning or contract ownership. Provide a context mapping framework with relationship map, ownership matrix, translation decisions, and versioning or failure policies. | pass→pass | 39,235 | 20,241 | -48% | 1 | 1 | 0% | 7,341 | 3,494 | -52% | 0 | 0 | — |
▸case-12 Our Identity and Access Management context provides authentication tokens to 12 downstream microservices. Downstream teams want IAM to accept custom user profile fields tailored to each microservice's domain model. Define a context map detailing relationship patterns, contract ownership, translation rules, and coupling risk mitigations. | pass→pass | 21,834 | 22,689 | +4% | 1 | 1 | 0% | 3,510 | 4,074 | +16% | 0 | 0 | — |
▸case-13 We are migrating a monolithic ERP into three bounded contexts: Inventory, Procurement, and Sales. During phase 1, Sales must read directly from the monolithic database while Inventory uses a new database. Map out this interim context integration specifying context pairs, relationship patterns, contract ownership, translation or ACL decisions, and risks. | fail→pass | 18,162 | 16,264 | -10% | 1 | 1 | 0% | 3,029 | 2,976 | -2% | 0 | 0 | — |
▸case-14 An Event Ticketing system has a Seat Reservation context and a Payment Processing context. Seat Reservation needs to hold seats for 10 minutes, but Payment Processing occasionally experiences 30-second latency spikes or timeouts. Create a context map detailing relationship patterns, contract ownership, translation logic, and failure or fallback behaviors. | pass→pass | 29,565 | 21,968 | -26% | 1 | 1 | 0% | 3,997 | 3,981 | -0% | 0 | 0 | — |
▸case-15 Our Fleet Management context needs telemetry data from an IoT Ingestion service. IoT Ingestion emits high-frequency binary Protobuf messages. Fleet Management's internal domain operates on rich domain objects with geospatial calculations. Map this context integration specifying relationship patterns, ownership, translation rules, and coupling risks. | pass→pass | 19,088 | 19,333 | +1% | 1 | 1 | 0% | 3,243 | 3,463 | +7% | 0 | 0 | — |
▸case-16 A media streaming platform has a Content Catalog context and a Search Indexing context. Search Indexing blindly copies all Content Catalog database tables via change data capture and relies on internal Catalog database column names in its search queries. Map out this integration with relationship map, ownership matrix, translation decisions, and risk mitigations. | pass→pass | 24,724 | 16,662 | -33% | 1 | 1 | 0% | 3,963 | 2,901 | -27% | 0 | 0 | — |
▸case-17 In a banking system, the Loan Origination context depends on Credit Scoring context. Credit Scoring is provided by a third-party credit bureau with strict REST API contracts and SLA penalties for bad requests. Map the context relationship specifying relationship patterns, contract ownership, translation logic, and failure modes. | pass→pass | 22,025 | 17,161 | -22% | 1 | 1 | 0% | 3,453 | 3,076 | -11% | 0 | 0 | — |
▸case-18 Our HR context and Payroll context were written by separate vendors. Payroll requires employee data in XML format fixed to a 2015 schema standard, while HR uses JSON REST APIs. Map out the integration between HR and Payroll including context pairs, relationship patterns, contract ownership, translation decisions, and risk mitigations. | pass→pass | 20,502 | 17,576 | -14% | 1 | 1 | 0% | 3,333 | 3,099 | -7% | 0 | 0 | — |
▸case-19 A SaaS application has a Billing context and a Customer Subscription context. The Subscription team routinely modifies domain event schemas without notifying Billing, breaking invoice generation. Map the context integration with context pairs, relationship patterns, contract ownership matrix, translation decisions, and failure or versioning policies. | pass→pass | 29,661 | 18,314 | -38% | 1 | 1 | 0% | 4,778 | 3,203 | -33% | 0 | 0 | — |
▸case-20 We are designing internal classes for our Order entity within a single monolith module. We need to decide whether the Order class should use the Builder pattern or Factory pattern to construct internal OrderItem value objects, and how getters or setters should be encapsulated. Provide internal class design guidance for this single service. | fail→pass | 18,724 | 12,660 | -32% | 1 | 1 | 0% | 3,255 | 2,216 | -32% | 0 | 0 | — |
▸case-21 We are deciding on cloud infrastructure tooling for our application. Should we host our microservices on AWS EKS or AWS ECS, and should we use Terraform or Pulumi for infrastructure provisioning? Provide a cloud infrastructure decision matrix. | fail→fail | 33,303 | 12,302 | -63% | 1 | 1 | 0% | 2,902 | 2,239 | -23% | 0 | 0 | — |
▸case-22 We need the exact OpenAPI 3.0 YAML schema definition for our POST /v1/customers REST API endpoint, including JSON schema data types, required fields, HTTP status codes 200, 400, and 500 responses, and header parameters. Draft the complete OpenAPI specification. | fail→fail | 23,326 | 19,055 | -18% | 1 | 1 | 0% | 5,326 | 4,735 | -11% | 0 | 0 | — |