Need for better Notification service GCP implementation "subscriber-control-topic" subscriptions management approach
This issue is created on the @Rustam_Lotsmanenko comment in the MR !235 (comment 133946)
The text of the comment is:
"... we may consider discussing the logic of the Notification service related to subscription configuration ...
I see two problems related to the current Notification service logic related to dynamic subscriptions, first is using a message broker as a "source of truth", and I believe we should move it from querying message broker to querying the database where info about subscriptions created via Register service should be.
The second one is a bit heavy way of handling with dynamic creation of subscriptions per each service replica, maybe later we could consider to use a bit lightweight solution like Redis Pub/Sub, where each replica can open a listener channel that can be automatically closed on shutdown and does not require additional handling."
I invite dear colleagues @andrei_dalhikh @Yauhen_Shaliou @Rustam_Lotsmanenko @Stanislav_Riabokon to the discussion. My opinion I will share right now as a first comment to the Issue.