NATS Micro input/output

[joeblew999]

NATS Micro input/output

Bento has nats and nats_jetstream, but not NATS Micro.

NATS Micro adds service registration via $SRV subjects, automatic discovery (gateways find services by name, not hardcoded subjects), health checks and stats at $SRV.PING, $SRV.INFO, $SRV.STATS, and load balancing across instances with same service name.

Bento as gateway (front):

HTTP → Bento → NATS Micro request → services → reply → Bento → HTTP response

input:
  http_server:
    path: /api/extract

pipeline:
  processors:
    - nats_micro:
        urls: [nats://localhost:4222]
        service: document-processor
        endpoint: extract

output:
  http_server: {}

Bento as service (behind gateway):

HTTP → narun → NATS Micro → Bento → reply → narun → HTTP response

input:
  nats_micro:
    urls: [nats://localhost:4222]
    name: document-processor
    endpoint: extract

output:
  nats_micro: {}

Both modes can publish progress to JetStream for SSE streaming via nats2sse.

Related: narun - HTTP/gRPC gateway → NATS Micro