From One Source to Many Channels: A Mail-Independent Notification Architecture — Part I

When notifications depend solely on email, all communication halts if email fails. (Part I)

Introduction

This article proposes an architecture where a notification is produced once from shared templates and dispatched to all active channels; email is one channel among several.

Method and Design

Each channel implements a shared interface and checks its own availability; if email is unconfigured its channel deactivates while others continue.

Discussion

The WhatsApp channel runs via a Node.js sidecar; the Telegram channel uses the official bot API; both are toggled by the administrator.

Adding Slack or SMS later means writing and registering a single class that reuses existing templates.

The Telegram bot also lets authors query article status in four languages, responding only to linked accounts.

Conclusion

This improves reliability and frees the journal from depending on a single channel.

This part demonstrates the platform's approach on a concrete journal example; the aim is to meet the complex requirements of scholarly publishing with a simple, sustainable architecture. Future work will examine how the model behaves at larger scale and across disciplines.