Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Register
  • Sign in
  • N Notification
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
    • Locked files
  • Issues 2
    • Issues 2
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 6
    • Merge requests 6
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Terraform modules
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Open Subsurface Data Universe SoftwareOpen Subsurface Data Universe Software
  • Platform
  • System
  • Notification
  • Issues
  • #25
Closed
Open
Issue created Jun 11, 2021 by Nikhil Singh[MicroSoft]@NikhilSinghMaintainer

Notification service redesign to avoid push event through public endpoint of our cluster

The idea is to make notification service extensible so it can ingest notifications from any intermediate Message brokers with minimum changes. The following cases would be covered under the scope of the problem:

1-Push Based Message Brokers :

The current implementation exposes the endpoint but it is not extensible enough to support multiple push based message brokers. Support for this will be provided in the redesigning which will enable the use of various message brokers efficiently.

2-Pull based Message Brokers:

Implementation of pull based Message broker will be provided at azure CSP level keeping the extensibility under consideration

3-Pull - Push Messaging Model:

Support for the messaging Model which includes the combined usage of Event Grid + Service Bus

RedesignNotificationService

Edited Jun 29, 2021 by Nikhil Singh[MicroSoft]
Assignee
Assign to
Time tracking