Notiva MS

Overview

Notiva MS is a multi-channel notification platform designed to centralize, process, and monitor communications across multiple applications and organizations. The system uses a microservices architecture and a multi-tenant model to separate responsibilities, isolate each organization's data, and allow individual components to scale independently.

The challenge

The main challenge was preventing every application from independently implementing delivery logic, retries, permissions, tracking, and usage control. The platform also needed to decouple business processes from external providers, maintain traceability for every notification, and provide a consolidated view of usage across different environments.

The solution

I designed a microservices-based architecture with asynchronous processing powered by BullMQ and Redis. Requests are validated through a central API and processed by independent workers. Email delivery is integrated with Resend through a provider abstraction layer. The platform includes organizations, roles, permissions, status tracking, and internal counters combined with provider metrics as the reference for actual consumption.

Role & contributions

I designed and implemented the overall platform architecture. My main contributions include:

• Designing the multi-tenant model.
• Managing organizations, members, roles, and permissions.
• Implementing queues and workers with BullMQ.
• Integrating Resend.
• Defining retry and error-handling strategies.
• Tracking the notification lifecycle.
• Designing usage counters and metrics.
• Separating business logic from external provider integrations.

Technologies

• TypeScript
• Node.js
• Microservices
• BullMQ
• Redis
• Resend
• REST APIs
• Multi-tenant architecture
• Role-based access control
• Background workers
• Asynchronous processing

Results

Notiva MS consolidates notification management into a centralized, decoupled platform designed for future growth. The solution reduces duplicated logic across applications, improves resilience to external provider failures, allows processing components to scale independently, and provides better traceability for deliveries, permissions, and usage.