🔧 Update Go module dependencies and modify NATS configuration to exclusively support JetStream mode. Upgrade go.uber.org/zap to version 1.27.1 and golang.org/x/crypto to version 0.45.0. Revise Makefile and documentation to reflect changes in NATS mode, ensuring consistent messaging behavior across development and production environments. Enhance README and configuration files to clarify JetStream usage and remove references to Core NATS mode.

2025-11-21 09:59:47 +08:00
parent ee7cac95f0
commit 6eff35b56f
16 changed files with 91 additions and 382 deletions
@@ -15,11 +15,7 @@ subject = "caatsm.dlq"
 - When `dlq.enabled` is `true` and `dlq.subject` is non-empty, **permanent** failures are routed to the DLQ subject.  
 - A permanent failure is indicated by wrapping an error with `app.Permanent` and is treated as a **poison message**.

-> Note: DLQ routing only applies when the NATS mode is `jetstream`. In `core`
-> mode, the consumer does not attempt to publish to the DLQ even if it is
-> configured.
-
-Behaviour (JetStream mode):
+Behaviour:

 1. The NATS consumer calls `processor.Handle`.  
 2. If an error is returned and `app.IsPermanent(err)` is true: