Honest ADR that talked me out of Kafka for a low-volume feature and into Postgres NOTIFY

You are a Staff Engineer responsible for architecture governance at a scale-up company. Write a comprehensive Architecture Decision Record. **Decision Title**: {{decision_title}} **Context/Background**: {{context_background}} (what situation led to this decision being needed?) **Options Under Consideration**: {{options_considered}} (list the specific technologies or approaches being compared) **Decision Drivers**: {{decision_drivers}} (what factors are most important: performance, cost, team expertise, time to market, etc.) Generate a complete ADR following this structure: 1. **ADR Metadata** - Number (e.g., ADR-042), Title, Status (proposed/accepted/deprecated/superseded), Date, Deciders 2. **Context and Problem Statement** - 2-3 paragraphs describing the forces at play (technical, political, social, project-local) 3. **Decision Drivers** - Prioritized list of factors with weightings (e.g., Performance: 30%, Cost: 25%, Team Expertise: 20%, Time to Market: 15%, Ecosystem: 10%) 4. **Considered Options** - Detailed description of each option with: - Description - Pros (numbered list) - Cons (numbered list) - Mitigations for each con 5. **Decision Outcome** - The chosen option with clear justification referencing decision drivers 6. **Consequences** - Separate lists for: - Positive consequences (becomes requirements) - Negative consequences (becomes risks to monitor) - Neutral consequences (things that change but aren't good or bad) 7. **Validation** - How we'll know this decision was correct (metrics, review date, success criteria) 8. **Prospects of Reversal** - Under what conditions this ADR would be revisited or superseded 9. **Related Decisions** - Links to related ADRs, dependencies on other decisions, decisions this enables 10. **Notes** - Meeting notes, discussion points, dissenting opinions and why they were considered but overruled 11. **Compliance Check** - How to verify this decision is being followed (automated linting, code review checklist, architecture review) 12. **Appendix** - Benchmarks, proof-of-concept results, references, vendor documentation links Use the Nygard ADR format with Michael Keeling extensions. Be honest about trade-offs and negative consequences.