Architecture Decision Record (ADR) Template with SQS vs. Kafka Example

As an expert technical writer with a deep understanding of software architecture and documentation best practices, your task is to generate a comprehensive document. This document will provide both a general-purpose Architecture Decision Record (ADR) template and a concrete example of an ADR.

### Role
You are an experienced technical writer specializing in documentation for engineering teams. You understand the importance of clear, concise, and structured communication of architectural decisions.

### Context
Architecture Decision Records (ADRs) are short text documents that capture a single architectural decision, its context, the options considered, and the chosen solution's consequences. They serve as a crucial historical log and communication tool for engineering teams. The objective is to equip teams with a reusable template and a practical, well-articulated example.

### Task
Produce a document containing two main sections:
1.  **ADR Template:** A markdown-formatted, general-purpose template for an Architecture Decision Record.
2.  **ADR Example:** A complete, filled-out Architecture Decision Record example, using the template, for the decision of choosing between SQS and Kafka as an event bus.

The overall output document must adhere to the following structure:

#### Overview
Introduce the purpose of the document: providing an ADR template and a practical example to guide engineering teams in documenting architectural decisions.
#### Prerequisites
List any knowledge or context an engineering team would need before effectively using ADRs (e.g., understanding the system's architecture, decision-making process).
#### ADR Template
Present the markdown-formatted ADR template. This template should include the following core sections:
*   **Title:** A concise name for the decision.
*   **Status:** Proposed, Accepted, Rejected, Superseded.
*   **Context:** The technical problem or challenge being addressed.
*   **Decision:** The chosen solution and rationale.
*   **Consequences:** Positive and negative implications, and future considerations.
*   **Alternatives Considered:** Other options evaluated and why they were not chosen.
#### ADR Example: SQS vs. Kafka Event Bus
Present the filled-out ADR example. This example should detail the decision-making process for selecting between SQS and Kafka for an event bus in a microservices environment. Ensure the example clearly articulates:
*   The specific problem (e.g., need for asynchronous communication, decoupled services).
*   The options (AWS SQS, Apache Kafka).
*   Evaluation criteria (e.g., cost, scalability, operational overhead, message durability, ordering guarantees, integration complexity).
*   The chosen solution and its justification based on a hypothetical scenario (e.g., initial focus on simplicity and managed service, scaling later).
*   The known consequences and trade-offs of that choice.
#### Verification
Explain how an engineering team can verify the ADR's effectiveness (e.g., peer review, ability to understand the decision months later).
#### Troubleshooting
Provide guidance on common issues when writing ADRs (e.g., too much detail, too little detail, lack of consensus).
#### Related Links
Suggest resources for further reading on ADRs, SQS, and Kafka.

### Constraints
*   The tone must be precise, professional, and respectful of the reader's intelligence. Avoid jargon-for-jargon's-sake.
*   The ADR template should be easily copy-pastable and usable in a markdown file.
*   The example ADR should be realistic and detailed enough to serve as a practical guide.
*   Emphasize clarity and conciseness in both the template and the example.
*   The decision in the example ADR should consider the {{team_size}} and {{current_infrastructure_stack}} to make the rationale more concrete.
*   Ensure all sections of the overall document structure are present and adequately detailed.

### Output
A single, coherent document structured as described above, containing both the ADR template and the specific SQS vs. Kafka example.