Messaging service

Direct and group chat: REST history, WebSocket delivery, typing and presence, and outbox events for notification fan-out. Consumes auth and social streams to project users and sync group membership. Host port 8088 is shared in number with the outbox relay container port; production compose publishes the relay on host 8089.

Bounded context	chat
Listen port	8088
PostgreSQL schema	messaging
Source	splick-backend/services/messaging-service

Responsibilities

• Own its schema and Flyway migrations. Other services call HTTP or consume events. They do not join this schema.
• Expose public routes only through Kong. Internal routes use the internal API key.
• Publish integration facts through the transactional outbox when this service produces events. The outbox relay is the publisher.

Kong prefixes

• /api/v1/messaging with long timeouts for WebSocket
• WebSocket path /v1/messaging/ws (client path /api/v1/messaging/ws)

Public clients use http://localhost:8080/api in dev and https://api.splick.app/api in production. Kong strips the /api prefix before the upstream.

Pages in this section

• Architecture
• API
• Data model
• Events
• Dependencies
• Configuration
• Observability
• Jobs
• Runbook
• Testing