Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • S Storage
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 46
    • Issues 46
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • Merge requests 21
    • Merge requests 21
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Container Registry
    • Infrastructure Registry
  • 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
  • Storage
  • Issues
  • #43
Closed
Open
Issue created Jan 18, 2021 by ashley kelham@kelhamMaintainer

The same topic exposes the Record Changed event and Record indexed event

The Azure implementation exposes multiple different system events through the same topic.

There are different use cases where this is undesirable.

For instance the notification service should only expose the Record changed events, but it receives all messages and forwards them on. This incurs extra running costs and complexity to clients who need to filter out messages.

The same applies to internal consumers of the event who subscribe directly to the topics.

One solution is to split the different messages between different topics and let clients explicitly chose which to subscribe to. However this close to R3 this is perhaps too big a change.

Another solution then is to add an extra property onto the messages and make use of the filtering mechanisms in service bus/event grid to filter based on this property e.g. message: recordchanged | recordindexed.

Edited Jan 18, 2021 by ashley kelham
Assignee
Assign to
Time tracking