What is the best way to organize the notification infrastructure at the microservice level?

Question

Database

There is a medium-sized project with an API Gateway and microservices that need to communicate with each other and, with certain CRUD operations, notify the desired group (s) of users. If, for example, new content has appeared in the database, you need to send notifications (user's choice: push, email, client-side socket messages...). Or, when a new message is received, display the number of new, unread messages. What are the best practices for displaying notifications if they are added to the RabbitMQ queue while the user is offline? Is it just to take them from a separate database of the "Notifications" microservice, or are there other options?

Answer 1

Found the answer on the net. They say you still need to use a separate database.