Repository navigation
Backend Realtime Chat Jobs
Chat, push notifications, and background automation. Architecture context: Realtime and Notifications. Part of Backend Overview.
Realtime here is Stream Chat + BullMQ, not Socket.IO.
socket.iois an installed dependency but no Socket.IO server is wired; the Redis/Socket.IO event bus indocs/guide/realtime-backend.mdis a design, not current code.
- Router
chat.router.ts(ChatController); webhookChatWebhookController.handleStreamEventat the raw-body route/v1/chat/webhooks/stream. - Services:
chat.service.ts(StreamChat.getInstance,ChatServiceError, appointment chat windows),networkChat.service.ts(colleague/network chat),sharedChatEntity.service.ts. - Model
chatSession.ts. Upload policyconfig/stream-upload-policy.tspushesBLOCKED_UPLOAD_EXTENSIONSto Stream at boot. - The Support Chat plans add a
SUPPORTsession type on this same infrastructure.
- Routers:
notification.router.ts(NotificationController),deviceToken.router.ts,marketing-unsubscribe.router.ts. - Services:
notification.service.ts,deviceToken.service.ts,marketing-unsubscribe.service.ts,contact-us.service.ts; utilsnotificationTemplates.ts,org-usage-notifications.ts,email.ts,email-templates.ts. - Models:
contect-us.ts(sic); notification and device-token entities are Prisma-only since PR #1819. - Delivery: mobile push via
firebase-admin(FCM); email via AWS SES/Pinpoint. Setup: Notifications Setup.
Config queues/bull.config.ts (redisConnection, defaultQueueOptions); orchestration queues/index.ts (initQueues()) and workers/index.ts.
| Domain | Queues / schedulers | Workers |
|---|---|---|
| Appointments |
appointment.queue.ts (MARK_NO_SHOW), appointment.scheduler.ts
|
appointment.worker.ts |
| Tasks |
task.queues.ts, task.schedulers.ts, task-schedule.queue.ts, task-schedule.scheduler.ts
|
taskRecurrence/taskReminder/taskSchedule.worker.ts
|
| Labs (IDEXX) |
idexx-reference.*, lab-status.*, lab-results.*
|
idexx-reference/lab-status/lab-results.worker.ts
|
There is no central EventBus module; decoupling is via these BullMQ queues plus FinanceEventService for finance events.
Home · Architecture · ADRs · Plans · Roadmap · Contributing · Main repo · DeepWiki · Discord
Yosemite Crew is a product of DuneXploration UG (haftungsbeschränkt). This wiki mirrors the repository; where a page and the repo disagree, the repo wins. See the Wiki Style Guide.
Product & Domain
Architecture
Applications
- Backend — Overview
- Frontend / PIMS Web — Overview
- Mobile — Overview
- Desktop PIMS Shell
- Developer Portal
- SuperAdmin
Design & Accessibility
Engineering Handbook
Decisions (ADRs)
Design Docs & Plans
Meta
Canonical code & docs: main repo · Auto-generated companion: DeepWiki