[Backend][Scalability][P3] Plan Background Job for Application Notifications (Future)

[AnshRaj112]

Backlog ID: ISSUE-EXS-073

Source: EXSOLVIA_GITHUB_ISSUES.md / EXSOLVIA_TECHNICAL_AUDIT.md

---

Title

[Backend][Scalability][P3] Plan Background Job for Application Notifications (Future)

Type

Architecture

Repository

@EXSOLVIA-frontend

Ownership

Backend + Architecture

Area

Background Processing

Priority

P3

Severity

Low

Labels

backend architecture P3

Epic

EPIC-12 Scalability & Production Readiness

Description

No queues; applications only write Mongo. Audit says when volume grows, move notify-admin off request path.

Current Behavior

No email/notify pipeline.

Expected Behavior

Design note + optional queue when notifications added — not premature Kafka.

Why This Matters

Keep HTTP fast when notifications appear.

Affected Files

• applications route
• future worker

Affected Functions / APIs

• POST /api/applications

Evidence From Audit

Audit Background Jobs.

Risk / Impact

Slow requests if sync email added naively later.

Recommended Direction

If adding email, use queue; until then document constraint.

Acceptance Criteria

• ADR or note exists before email feature
• No sync SMTP in request without timeout/queue plan

Testing Requirements

• Regression test

Dependencies

• None

Estimated Complexity

Large

Priority Reason

Forward-looking; low urgency now.

Notes

Do not over-engineer before notifications exist.