Angularfire and NodeJS firebase chat application by using topics

I'm a newbie on the firebase. I'm trying to make a chat application with multiple users and multiple rooms by using `AngularJS` (`angularfire`) for the frontend and `NodeJS` for the backend. I want to send many-to-many notifications. I'll use `topics` for this.

Here are the steps I followed:

1. Register user to firebase (backend-NodeJS)
2. Save user UID to the database (MongoDB)
3. Subscribe this user to the topics (backend-NodeJS)
4. Receive notifications from the topics which user has subscribed (frontend-Angular)

I can listen notifications by using `AngularFireMessaging` module (requesting permission and listening) by using these methods in my app.component.ts:

```typescript
@Component({
selector: 'app-root',
templateUrl: './app.component.html',
styleUrls: ['./app.component.scss'],
})
export class AppComponent implements OnInit {
constructor( private afMessaging: AngularFireMessaging ) { }

ngOnInit(): void {
this.requestPermission();
this.listen();
}

requestPermission() {
this.afMessaging.requestPermission
.pipe(mergeMapTo(this.afMessaging.tokenChanges))
.subscribe(
(token) => { console.log('Permission granted! Save to the server!', token); },
(error) => { console.error(error); },
);
}

listen() {
console.log('messages are being listened');
this.afMessaging.messages
.subscribe((message) => {
console.log("messages from firebase");
console.log(message);
});
}
}
```

But as I understand this just registers the token and listens it.

I know I can use realtime databases of firebase. But the app is already prepared and we're storing users' UIds in the database. Also chat rooms and users' relations are also stored in the database.

I thought I can send notifications to the `topic`s named as `roomId`s. Then I can listen these topics.

But how can I listen these topics? I have `topic`'s names, I have also users' UIds. How can I listen these topics?

Or am I missing something?

Start with the notification flow in app.component.ts, especially requestPermission() and listen(), then review the NodeJS topic-subscription steps and the MongoDB user and room relationships. Done means defining how roomId topics are subscribed to and received for the existing Angular and NodeJS application.

Written by the indexing model from the issue text.