[Performance] SMS log aggregator holds up to 5,000 records in memory with no persistence

[RUKAYAT-CODER]

Overview

src/lib/logging/sms-aggregator.ts stores all SMS log records in a module-level array capped at 5,000 entries. In a high-volume SMS scenario this consumes significant heap memory, and all data is lost on server restart — making it impossible to query historical delivery metrics or troubleshoot past failures.

Specifications

Features:

• SMS logs are written to a persistent store (database or append-only log file)
• In-memory buffer is small (e.g., 100 entries) for fast recent-query access only

Tasks:

• Add a database table sms_logs with columns for all fields tracked by the aggregator
• Flush the in-memory buffer to the database on a configurable interval or when the buffer reaches capacity
• Update query methods to fall back to database queries for historical data

Impacted Files:

• src/lib/logging/sms-aggregator.ts
• src/lib/db/ (new migration)

Acceptance Criteria

• SMS logs survive a server restart
• Historical queries beyond the in-memory buffer hit the database
• Memory usage does not grow with SMS volume

[Neche58]

@Neche58 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

hi maintainer i will like to work on this issue

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Neche58 to this issue.

[dot-enny]

@dot-enny has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi maintainer, can i work on this ? ETA - within the hour to 8 hours max.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @dot-enny to this issue.

[Chrisland58]

@Chrisland58 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hi Rina please assign me just one issue please

ℹ️ Repo Maintainers: To accept this application, review their application or assign @Chrisland58 to this issue.

[nanaabdul1172]

@nanaabdul1172 has applied to work on this issue as part of the Stellar Wave Program's 6th wave.

Hello,

I am excited to contribute to this issue. I have experience collaborating on open-source projects and understand the importance of clear communication and reliable delivery. If assigned, I will provide consistent progress updates and a well-tested implementation.

I would appreciate the opportunity to work on this issue.

ℹ️ Repo Maintainers: To accept this application, review their application or assign @nanaabdul1172 to this issue.

[drips-wave]

Congratulations, @nanaabdul1172! 🎉 Your application was accepted by the repo's maintainers, and the issue is due on June 30, 2026.

🧑‍💻 @nanaabdul1172: Please resolve the issue such that the repo's maintainers have enough time to review your contribution before the due date. You'll earn Points for completing the issue on-time, which will make you eligible for a share of the Stellar Wave Program's reward pool.

Warning

When opening a PR, please link it to this issue to ensure it gets tracked accurately. Points are awarded when this issue is marked as completed by the maintainer.

🤠 Repo maintainers: Please keep an eye on the contributor's progress and review their work before the due date. You can manage this issue, including adjusting its complexity and points, here.

🌊 Happy Wave 🌊