AWS SQS / Background Queue

1. Business Summary

Uses AWS SQS (and local cron_job_sqs table) for background dispatch: security cron, ready-mails, message ingest, etc.

2. Business Value

Decouples expensive operations; resilience.

3. Users / Stakeholders

System.

4. Workflows

• sendSQSMessage() enqueues messages.
• recieveMessage()/recieveMessageSecurity() consume.
• Many crons coordinate with SQS for scaling.

5. Sub-Features

• cron_job_sqs table for security queue.
• AWS SQS for distributed dispatch.

6. Business Rules

• Idempotency expected per consumer.
• Retry tied to consumer logic.

7. Data Entities

cron_job_sqs.

8. Entry Points

• common_crons/sendSQSMessage, recieveMessage, recieveMessageSecurity.

9. Inputs & Outputs

• Inputs: messages.
• Outputs: side-effects on consumers.

10. Integrations

• AWS SQS.

11. Calculations / Logic

• N/A.

12. Status Lifecycle

• Queue states (sent, received, processed).

13. Permissions

• Service-level.

14. Reports & KPIs

• Queue depth, dead-letter counts.

15. Risks & Observations

• Failure visibility weak; no central dashboard observed.

16. Source Code Evidence

• app/Controller/CommonCronsController.php :: sendSQSMessage, recieveMessage, recieveMessageSecurity.