Skip to content

[Tech Debt] Event Persistence: Migrate Volatile PubSub to Redis Streams/RabbitMQ #4

@genesisgzdev

Description

@genesisgzdev

Current State: The system utilizes standard Redis PubSub (pubsub.service.ts), which is fire-and-forget. If an API pod crashes (OOM, eviction) during an event emission (e.g., ticket purchased), the webhook or email is never processed.

Required Action: Migrate the service to Redis Streams or RabbitMQ to guarantee event delivery via consumer groups and acknowledgements (Dead Letter Queue routing for retries).

Metadata

Metadata

Assignees

No one assigned

    Labels

    critical-debtCritical architectural flaw that can cause data losshigh-priorityMust be addressed in the next sprint

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions