PulseNotify

PulseNotify is an enterprise-grade, highly scalable distributed notification service designed to handle millions of notifications across various channels, including Email, SMS, and Push.

This project is built to demonstrate advanced system design, event-driven architecture, and robust cloud deployment practices suitable for a production environment.

Tech Stack

Backend:

• Java 21 & Spring Boot 3
• PostgreSQL & Spring Data JPA
• DynamoDB (Rate Limiting & Tokens)
• Spring Security (JWT + RBAC)
• AWS SQS & AWS Lambda (SAM)

Frontend:

• React 18 & TypeScript
• Vite
• React Query & Axios

DevOps & Cloud:

• Docker & Docker Compose (For Local Development)
• Vercel (Frontend Hosting)
• AWS SAM (Serverless Application Model)
• AWS Lambda, API Gateway, RDS, DynamoDB, SQS

System Architecture & Workflows

1. Modular Architecture

graph TD
    Client[Frontend: React/Vite App on Vercel] -->|HTTPS| APIGW[AWS API Gateway]
    APIGW --> SpringBoot[Spring Boot on AWS Lambda]
    
    subgraph Serverless Spring Boot
        Auth[Auth Module]
        Template[Template Module]
        Notif_API[Notification Module]
        Analytics[Analytics Module]
        Scheduler[Scheduler Component]
    end

    Auth --> DB[(PostgreSQL RDS)]
    Auth --> DDB[(DynamoDB)]
    Template --> DB
    Notif_API --> DB
    Notif_API --> DDB
    Analytics --> DB

    Scheduler -->|Poll scheduled & Move to SQS| SQS_Main
    Notif_API -->|Publish| SQS_Main[AWS SQS: Main Queue]

Loading

2. AWS Infrastructure (Deployed via SAM)

graph TD
    subgraph AWS Serverless Cloud
        Client[User / Web Browser] --> Vercel[Vercel Global Edge Network]
        Client --> APIGW[Amazon API Gateway]
        
        APIGW --> LambdaBoot[AWS Lambda: Spring Boot]
        
        LambdaBoot --> RDS[(Amazon RDS - PostgreSQL)]
        LambdaBoot --> DDB[(Amazon DynamoDB)]
        
        LambdaBoot -->|Publish| SQS[Amazon SQS Main Queue]
        SQS --> LambdaWorker[AWS Lambda: SQS Consumer]
        LambdaWorker --> SES[Amazon SES: Email Provider]
        LambdaWorker --> MockSNS[Mock SMS Provider]
        
        LambdaWorker -->|Max Retries Exceeded| DLQ[SQS Dead Letter Queue]
    end

Loading

3. Notification State Machine

stateDiagram-v2
    [*] --> PENDING
    PENDING --> QUEUED : Published to SQS
    QUEUED --> PROCESSING : Lambda consumes
    PROCESSING --> SENT : Handed to Provider
    SENT --> DELIVERED : Provider Webhook
    
    PROCESSING --> FAILED : Error
    FAILED --> RETRYING : Under Max Retries
    RETRYING --> PROCESSING : SQS Retry
    
    FAILED --> DLQ : Max Retries Exceeded

Loading

4. Authentication Flows

User Login

sequenceDiagram
    participant Client
    participant AuthController
    participant AuthService
    participant DB as PostgreSQL
    participant JwtUtils

    Client->>AuthController: POST /api/v1/auth/login {email, password}
    AuthController->>AuthService: authenticateUser()
    AuthService->>DB: findByEmail()
    DB-->>AuthService: User Entity
    AuthService->>AuthService: Verify Password
    AuthService->>JwtUtils: generateJwtToken(UserDetails)
    JwtUtils-->>AuthService: Access Token
    AuthService->>AuthService: createRefreshToken(UserId)
    AuthService->>DB: Save Refresh Token
    AuthService-->>AuthController: JwtResponse (AccessToken, RefreshToken)
    AuthController-->>Client: 200 OK + JwtResponse

Loading

Refresh Token

sequenceDiagram
    participant Client
    participant AuthController
    participant RefreshTokenService
    participant DB as PostgreSQL
    participant JwtUtils

    Client->>AuthController: POST /api/v1/auth/refresh {refreshToken}
    AuthController->>RefreshTokenService: findByToken(refreshToken)
    RefreshTokenService->>DB: Query Token
    DB-->>RefreshTokenService: RefreshToken Entity
    RefreshTokenService->>RefreshTokenService: verifyExpiration()
    RefreshTokenService->>JwtUtils: generateTokenFromEmail(User.email)
    JwtUtils-->>RefreshTokenService: New Access Token
    RefreshTokenService-->>AuthController: TokenRefreshResponse (New Access Token)
    AuthController-->>Client: 200 OK + TokenRefreshResponse

Loading