3 min read
ADR-0001: Use Apache Kafka for Inter-Service Communication Status Accepted Date 2025-11-15 Context Our platform has grown from 3 microservices to 12 over the past year. Services …
11 pages
Deal-Engines
2 min read
ADR-0002: Use AWS SQS for Asynchronous Inter-Service Communication. (from ChatGPT) Status Accepted Date 2026-08-31 Context As Deal Engine extracts capabilities from the existing …
7 min read
ADR-0001: Use Amazon SNS + SQS for Inter-Service Communication (Claude) Status Accepted Date 2025-11-15 Context Our platform has grown from 3 microservices to 12 over the past …
4 min read
ADR 003: Choice of Message Broker for Asynchronous Job Orchestration Google Cloud Tasks vs. Google Cloud Pub/Sub This record documents the architectural reasoning for transitioning …
5 min read
ADR 003: Message Broker Selection for Asynchronous Job Orchestration Replacing NoSQL Polling The current reliance on NoSQL polling for core transactional workflows has reached its …
3 min read
ADR-0023: Use Apache Kafka for Inter-Service Communication Status Accepted Date 2025-11-15 Context Our platform has grown from 3 microservices to 12 over the past year. Services …
1 min read
ADR-NNNN: [Short Title Describing the Decision] Status [Proposed | Accepted | Deprecated | Superseded by ADR-XXXX] Date [YYYY-MM-DD] Context [Describe the situation. What problem …
6 min read
For Deal Engine, I’d make the ADR much more specific than “migrate the monolith to microservices.” An ADR should capture one architectural decision. Given their domain and the …
9 min read
ADR-0023: Use AWS SQS and SNS for Asynchronous Inter-Service Communication Status Accepted Date 2026-08-31 Context Deal Engine is progressively moving functionality from the …