✨ Implement dead-letter queue (DLQ) functionality for handling permanent failures in message processing. Update configuration to enable DLQ and specify the subject for routing failed messages. Enhance observability by adding metrics for message handling, retries, and database operations. Introduce structured logging for better traceability of message processing events.

2025-11-16 09:15:37 +08:00
parent c98baa0ff4
commit a96cb8a40b
12 changed files with 1053 additions and 31 deletions
@@ -21,6 +21,7 @@ type Config struct {
 	Publisher  PublisherConfig  `koanf:"publisher"`
 	Telemetry  TelemetryConfig  `koanf:"telemetry"`
 	Monitoring MonitoringConfig `koanf:"monitoring"`
+	DLQ        DLQConfig        `koanf:"dlq"`
 	// Legacy fields for backward compatibility during migration
 	Subscription SubscriptionConfig `koanf:"subscription"`
 	Timeouts     TimeoutsConfig     `koanf:"timeouts"`
@@ -93,6 +94,14 @@ type TelemetryConfig struct {
 	Insecure bool   `koanf:"insecure"`
 }

+// DLQConfig defines the dead-letter queue routing for poison/permanent messages.
+// If Enabled is true and Subject is non-empty, permanent failures will be published
+// to the configured subject for offline processing.
+type DLQConfig struct {
+	Enabled bool   `koanf:"enabled"`
+	Subject string `koanf:"subject"`
+}
+
 // MonitoringConfig controls the lightweight HTTP server that exposes health and metrics endpoints.
 type MonitoringConfig struct {
 	Disabled      bool          `koanf:"disabled"`