Rating & Notification Services

Problem

Ratings and notifications look related in a product, but they rot when forced into one blob. Different lifetimes, different failure modes, different scale pressures.

Approach

Separated rating capture from notification fan-out, then connected them with clear service boundaries instead of shared mutable shortcuts.

Architecture

• Rating service owns scores and review data
• Notification service owns delivery concerns
• Integration stays explicit — no silent cross-service writes

Outcome

A multi-service sketch that mirrors how I think about production systems: isolate change, make ownership obvious, keep the seams honest.