Is the use of message queues and an architecture with an event model justified?

Question

.NET

There is a service that accepts REST requests for some data samples. Changing and adding data is also carried out through it. It is necessary to notify the services that subscribe to this about the data change.
I thought about the architecture Data service -> Subscription manager (receives events and distributes messages to queues, also stores who subscribed to an event) -> Message queues -> Subscribers.
How do you think, is such an architecture justified? Maybe there is some well-known design pattern that did not see that it describes a similar task?

Answer 1

Described in Fowler's book, for example
https://www.enterpriseintegrationpatterns.com/patt...

Answer 2

I regularly use a similar design. A couple of points:
1. I never use external universal message queues (MSMQ etc). Instead, an easy, simple, customized solution for each specific case.
2. I always integrate into a single whole what you call "data service", "subscription manager" and "message queues".