issuetracker / Architecture / Integration Boundaries

Integration Boundaries

The issue tracker should isolate external integrations behind explicit interfaces.

1 min readApplies to v0.6.0
On this page ▾
  1. Principle
text
Issue Tracker
      │
      ├── Email
      │
      ├── Webhooks
      │
      ├── SSO / identity
      │
      ├── Storage
      │
      └── Background workers

Principle

External services should not leak provider-specific details throughout the domain layer.

Prefer:

text
domain/service
      │
      ▼
integration interface
      │
      ▼
provider implementation

This keeps provider replacement and testing manageable.