# Low-Level Design: [Component / Service Name]

**Parent HLD:** [Reference] · **Version:** [x.y] · **Date:** [YYYY-MM-DD] · **Author:** [Name]

## 1. Scope

Which specific component from the parent HLD this LLD covers — an LLD
should never try to cover an entire solution; if it does, it's really an
HLD wearing the wrong title.

## 2. Detailed Component Design

### 2.1 Internal Structure

Classes, modules or services and their responsibilities.

### 2.2 Data Model

Entities, fields, types and constraints — or a reference to the schema
file if the model is large.

```json
{
  "example": "entity structure — replace with your actual schema shape"
}
```

## 3. API Contract

### Endpoint: [METHOD] /path

**Request:**
```json
{}
```

**Response (200):**
```json
{}
```

**Error responses:**

| Code | Condition | Body |
|---|---|---|
| | | |

## 4. Sequence Diagrams

For each key flow: step-by-step interaction between components, including
the error and retry paths — not just the happy path.

## 5. Error Handling & Retry Logic

| Failure Mode | Detection | Response | Retry Policy |
|---|---|---|---|
| | | | |

## 6. Configuration

| Parameter | Purpose | Default | Environment-specific? |
|---|---|---|---|
| | | | |

## 7. Logging & Monitoring

- Key metrics to expose:
- Alert thresholds:
- Log levels and what triggers each:

## 8. Test Plan Summary

- Unit test coverage approach:
- Integration test scenarios:
- Key edge cases to cover:

## 9. Deployment Notes

Rollout approach, feature flags, and the rollback plan — an LLD without a
rollback plan is an LLD that assumes it will work first time.