Reusing Observables with named Observables?

[abarke]

I have a use case where we use a WebSocketSubject to connect to our backend where we can send JSON-RPC style messages to subscribe to various data sources using Multiplex. The problem is that we have many web components that require the same data.

The goal is to be able to reuse existing subscriptions between web components instead of subscribing twice to the same data source.

One way to solve this is by creating a Map that keeps track of all the registered observables created using Multiplex and give them a unique ID where

const observables = new Map();

// Store observables for later reuse
observables.set('aaa', Observable1);
observables.set('bbb', Observable2);
observables.set('ccc', Observable3);

// Create a new ID for the Observable
const newId = 'ddd'

// Check if a observable with an identifier exists and use it 
if (observables.has(newId)) {
  observables.get(newId).subscribe((data) => console.log(data))
} else {
  const observable = webSocketSubject.multiplex(() => 'sub', () => 'unsub', (msg) => msg.value)
  const subscription = observable.subscribe((data) => console.log(data))
  observables.set(newId, observable);
}

Ideally it would be nice to have RxJS keep track of all observables and allow developers to dig one out should it exist e.g.

const id = 'uniqueIdentifier'

// By adding an optional `id` parameter to multiplex, observables could be given an ID that can be queried.
if (webSocketSubject.observers.has(id)) {
  webSocketSubject.observers.get(id).subscribe((data) => console.log(data))
} else {
  webSocketSubject.multiplex(() => 'sub', () => 'unsub', (msg) => msg.value, id).subscribe((data) => console.log(data))
}

Does this make sense? overkill? or a better way of reusing subscriptions/observables/subjects?