Architecture hexagonale et système de notification scalable

1. ARCHITECTURE MULTITIERS
ET SYSTÈME DE
NOTIFICATION
Chercherunproduit.fr
Startpointlebanon.com

2. Architecture hexagonale du service
Heading
PHYSICAL TECHNOLOGY
COMP.
NotificationClient
Configuration
Configuration API
File Source
API
Accès aux
données
NoSQL
SQL Entity
Framework Core
SQL Server
In Memory
MiddleWare
Cluster
Standalone
Logging
Log4Net Adapter
Logging API
Telemetry
Telemetry
Azure App insight
Amazon Cloud
Watch
PHYSICAL TECHNOLOGY
COMP.
NotificationLive
Streamer Server
Redis
RavenDB
Cosmos SQL
DocumentDB
MongoDb
Server Sent Events

3. Architecture Logique
LOGICAL APPLICATION COMP.
EventLiveStreamerService:
Notification Server
PHYSICAL APPLICATION COMP.
EventLiveStreamerService.Api.SSE
SSE Implementation
INFORMATION SYSTEM SERVICE
Configuration
INFORMATION SYSTEM
SERVICE
Diagnostic
INFORMATION SYSTEM
SERVICE
Logging
LOGICAL APPLICATION
COMP.
ECommerce.Events.CallB
ackActions
CallBack Invoker
PHYSICAL APPLICATION COMP.
ECommerce.Events.CallBackActions.
AsyncEventMethodCallBack
Asynchrone method
PHYSICAL APPLICATION COMP.
ECommerce.Events.CallBackActions.
HttpMethodCallBack
http method
LOGICAL APPLICATION COMP.
EventLiveStreamer.
Notification Client
INFORMATION SYSTEM
SERVICE
Data Access component
LOGICAL APPLICATION COMP.
EventLiveStreamer.
Subscriber Client
PHYSICAL APPLICATION COMP.
API Rest Service

4. Architecture Physique
PHYSICAL TECHNOLOGY
COMP.
Notification Server
PLATFORM SERVICE
Data access component
PLATFORM SERVICE
Logging
PLATFORM SERVICE
Telemetry
PHYSICAL TECHNOLOGY
COMP.
Notification Client
PLATFORM SERVICE
Configuration
Publish
LOGICAL TECHNOLOGY
COMP.
CallBack Invoker
Invoke
PHYSICAL TECHNOLOGY
COMP.
Subscriber client

5. Mode d’utilisation
■ Utilisation en 2 composants ou regrouper en un seul
– Le service de notificationCentralisé et unifié
– L’écouteur d’événements répartis ou regroupés
■ Client de publication hébergé par votre application via une librairie .NET
PHYSICAL TECHNOLOGY
COMP.
Notification Subscriber
Site
PLATFORM SERVICE
CallBack Action
(Local or HTTP)
PHYSICAL TECHNOLOGY
COMP.
Application
http Siteor Mobile or
Native Client
LOGICAL TECHNOLOGY
COMP.
Notification Client
LOGICAL TECHNOLOGY
COMP.
Notification Subscriber
client
PHYSICAL TECHNOLOGY
COMP.
Notification Server
PLATFORM SERVICE
Data Access Component
PLATFORM SERVICE
Configuration

6. Cluster haute disponibilité et Haute
capacité
■ 2+ Instances du service notification
– Redondance des services, avec Un mécanisme de fallback
– Fallback : Un mécanisme de très haute disponibilité (Si aucun service de notification n’est
disponible, L’action est stockée en background)
■ 2+ Instances de l’écouteur
– Redondance des services (si Fifo) ou Parallélisation des traitement
PHYSICAL TECHNOLOGY
COMP.
Notification Subscriber
Site
PLATFORM SERVICE
CallBack Action
(Local or HTTP)
PHYSICAL TECHNOLOGY
COMP.
Application
http Siteor Mobile or
Native Client
LOGICAL TECHNOLOGY
COMP.
Notification Client
LOGICAL TECHNOLOGY
COMP.
Notification Subscriber
client
PHYSICAL TECHNOLOGY
COMP.
Notification Server
PLATFORM SERVICE
Data Access Component
PLATFORM SERVICE
Configuration
Redondance
Redondance
Haute capacité

7. Configuration du système
■ Repositories
– EventChannel (pour les channels)
– EventSubscription (pour les écouteurs)
– EventMessage pour les messages
– Type de paramétrage
■ Provider (Type de provider à utiliser)
■ ConnectionString (chaîne de connection)
■ Notification and Subscriber Clients
– NotificationUrls
– IntervalTimeOut
– RetryingCount
– Background Retrying Interval
PHYSICAL TECHNOLOGY
COMP.
Notification Service
LOGICAL TECHNOLOGY
COMP.
Data Access component
Provider
ConnectionString
PHYSICAL TECHNOLOGY
COMP.
Notification Client
Notification Urls
Interval Timeout
Retrying count
Background
Retrying interval
PHYSICAL TECHNOLOGY
COMP.
Subscriber Client
Notification Urls
LOGICAL TECHNOLOGY
COMP.
Configuration