Notification service

In-app notification inbox and mobile push (APNs, optional FCM). Materializes notifications from social, feed, expense, and messaging streams, stores device tokens, and dispatches push through a retry and dead-letter pipeline.

Bounded context	notifications
Listen port	8086
PostgreSQL schema	notification
Source	splick-backend/services/notification-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/notifications
• /api/v1/devices

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