Differences

This shows you the differences between two versions of the page.

--- api:notifications [2024/09/20 21:05] – [How does it work?] daniel
+++ api:notifications [2024/10/03 15:50] (current) – removed daniel
@@ Line 1: / Line 1: @@
-====== Notifications ======
-===== Notification Delivery Service =====
-The Notification Delivery Service is responsible for queuing notifications and delivering them to the provider’s APIs. This service supports sending Emails, SMS, push notifications and specific notifications to T4NotificationService.
-==== How does it work? ====
-{{ :api:delivery_service.jpg?400 |}}
-Our server sends objects to an Azure Service Bus, directing them to their respective queues. Each type of notification has its own dedicated queue. Azure Functions listen to these queues and are responsible for forwarding the messages to their destinations. The Azure queues are configurable, allowing customization of concurrency and retry policies to meet our specific requirements.
-==== How to use it? ====
-There is one class per type of notification you can send with Delivery Service, the classes are:
-  * EmailNotificationDeliveryService
-  * SMSNotificationDeliveryService
-  * PushNotificationDeliveryService
-  * NotificationBodyDeliveryService
-There are interfaces for each component, enabling the use of dependency injection in services and facilitating mocking in integration testing. Each class includes two types of constructors: a parameterless constructor that reads configuration from the app.config files, and another constructor that accepts Azure configuration directly, for services that do not use the app.config file.
-You can find code examples in the repo T4, file T4\System\Components\T4ServerUtil\Notification\DeliveryServices\EmailNotificationDeliveryService.cs this is a Unit Test repository and you can run the examples directly.