Skip to content
  • product-portfolio
  • ecosystem-catalog
  • deep-dives
  • core

Notifications, Messaging, Email, SMS & Webhooks - Analysis

Planning-layer analysis for category 5. It groups the 50 candidate services into capabilities, recommends what becomes a standalone service versus a module, and captures domain, interface, and non-functional notes. For the plain item list see the browse page.

Scope & Bounded Context

  • Primary bounded context: Notifications & Webhooks
  • Group: core
  • Default wave / cycle: Phase 1 · Core Platform Wave
  • Items: 50 candidates

This category is anchored to the ConnectSoft DDD baseline in the SaaS framework DDD blueprint and the service classification model.

Classification Breakdown

Classification Count
Connector 7
Microservice 2
Module-in-service 34
Platform Product 3
Portal/UI Module 4

Anti-fragmentation stance

Per ADR-0011, the 34 module candidates below are delivered inside the Notifications & Webhooks bounded-context service, not as separate microservices. Only the 5 platform/service candidates justify an independent runtime.

Standalone Service / Platform Candidates

ID Service Tier Status
CS-SVC-0201 Notification Platform 1 Documented
CS-SVC-0202 Email Platform 1 Documented
CS-SVC-0219 SMS Gateway 1 Documented
CS-SVC-0227 WhatsApp Messaging Gateway 1 Planned
CS-SVC-0241 Webhook Platform 1 Planned

Connector Candidates

  • SendGrid Adapter (CS-SVC-0205) - plugin in the Connector Runtime.
  • Mailgun Adapter (CS-SVC-0206) - plugin in the Connector Runtime.
  • Amazon SES Adapter (CS-SVC-0207) - plugin in the Connector Runtime.
  • SMTP Adapter (CS-SVC-0208) - plugin in the Connector Runtime.
  • Twilio Adapter (CS-SVC-0221) - plugin in the Connector Runtime.
  • Vonage Adapter (CS-SVC-0222) - plugin in the Connector Runtime.
  • MessageBird Adapter (CS-SVC-0223) - plugin in the Connector Runtime.

Portal / UI Modules

  • Email Template Designer (CS-SVC-0210)
  • Email Deliverability Dashboard (CS-SVC-0218)
  • Notification Preference Center (CS-SVC-0233)
  • Webhook Delivery Dashboard (CS-SVC-0247)

Domain, Interfaces & Data Ownership

  • Aggregates are owned by the Notifications & Webhooks context; cross-context reads go through published contracts, never shared databases.
  • Integration is event-first (outbox + integration events) per the event-driven mindset.
  • APIs are contract-first and versioned through the API & Integration context.

Non-Functional Posture

  • Multi-tenancy & edition-awareness: required for all serious candidates.
  • Security: Standard baseline; secrets via the platform secret store; least privilege.
  • Compliance: standard audit logging.
  • Observability: OpenTelemetry traces, metrics, and structured logs.

MVP vs Future

  • MVP (Tier 0-1): Notification Platform, Email Platform, Email Delivery Service, Email Provider Abstraction, SendGrid Adapter, Mailgun Adapter, Amazon SES Adapter, SMTP Adapter
  • Future (Tier 4-5): none

Open Questions

  • Which module candidates, if any, develop independent scaling or ownership needs that would justify promotion to a standalone service?
  • Where do this category's contracts overlap with adjacent contexts, and who owns them?