Skip to content

feat: switch on-demand tcp to persistent grpc channel for hi-prio messages - #45

Merged
gchiesa merged 2 commits into
mainfrom
ms-020-grpc-persistent-channel
Aug 15, 2026
Merged

feat: switch on-demand tcp to persistent grpc channel for hi-prio messages#45
gchiesa merged 2 commits into
mainfrom
ms-020-grpc-persistent-channel

Conversation

@gchiesa

@gchiesa gchiesa commented Aug 15, 2026

Copy link
Copy Markdown
Owner

What

  • Implemented persistent gRPC channels for high-priority messaging.
  • Updated Docker Compose configuration to modify the number of replicas.

Why

  • Persistent gRPC channels enhance the efficiency and reliability of high-priority message processing, reducing connection overhead.

Testing

  • Unit tests added / updated (mise run tests passes)
  • Linter passes (mise run lint passes)
  • Manually tested with the Docker Compose stack (deployments/docker-compose/)
  • No tests needed — explain why:

Checklist

  • Tracking issue is referenced above
  • Commit messages follow Conventional Commits format
  • Assisted-By trailers added where an AI assistant contributed
  • Documentation updated in docs/content/docs/ if behaviour changed

@gchiesa gchiesa changed the title Update Docker Compose replicas and implement persistent gRPC channels feat(ms020): switch on-demand tcp to persistent grpc channel for hi-prio messages Aug 15, 2026
@gchiesa gchiesa changed the title feat(ms020): switch on-demand tcp to persistent grpc channel for hi-prio messages feat: switch on-demand tcp to persistent grpc channel for hi-prio messages Aug 15, 2026
@gchiesa
gchiesa merged commit 3a2f2b7 into main Aug 15, 2026
11 of 13 checks passed
@gchiesa
gchiesa deleted the ms-020-grpc-persistent-channel branch August 15, 2026 07:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant