blnkfinance/blnk

Persist hooks to PG instead of Redis

Open

#225 opened on Dec 30, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (129 forks)auto 404
enhancementgood first issue

Repository metrics

Stars
 (475 stars)
PR merge metrics
 (PR metrics pending)

Description

Describe the bug Webhooks are being stored in Redis instead of a persistent database (PG). When Redis is restarted, all hooks created are lost, requiring them to be re-registered.

To Reproduce Steps to reproduce the behavior:

  1. Configure and register webhooks in core(using the pre or post hook endpoint)
  2. Verify webhooks are working correctly
  3. Restart the Redis instance
  4. Attempt to use or view previously configured webhooks
  5. Observe that all webhook configurations have been lost

Expected behavior Webhooks should persist across Redis restarts. They should be stored in a persistent database (PG) so that restarting Redis does not result in data loss.

Contributor guide

Research direction
Investigate the current webhook storage implementation in Redis. Identify where hooks are stored and retrieved. Design a migration to store them in PostgreSQL, including schema creation and data migration if needed. Update the data access layer to use PostgreSQL instead of Redis.
Tech stack
gopostgresqlredis
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
GitGoPostgreSQLRedis
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65